Two Server LAN...

I hope I'm posting in the right newsgroup.

I am not computer illiterate, but know little about LANs (just basic stuff),
and I am trying to set up a small business LAN (actually enhance one that I
inheritted). I'll briefly describe what I am trying to do. Any ideas you
can give me, what to avoid, pointers to good reference material, etc. would
be greatly appreciated.

- Existing NT4 Server with 6 clients
- Want to add a 2003 Small Business Server
- Want to add a wireless Router (for 3 tablet PCs and 3 Pocket Pcs)
- Want to add DSL acces to the net

Should the 2003 and NT be part of the same domain? Should I keep them
separate? At the end of the day, all I want is for the 6 (old) +6 (wireless)
clients to be able to access both servers, the servers to be able to access
each other, and for all clients to have access to the internet.

As I said, any ideas? Any traps to avoid? (like should I have fixed IP
addresses for each client, or set it up so that the server assigns them?
Which server should I use to manage that? etc.) Any pointers to good
reference material?

Thanks,
Gary

yes, they can be the same domain. it is better to install AC and DNS on the
2003. You may also need to install WINS since you have NT.

--
For more and other information, go to http://www.ChicagoTech.net

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

"Gary" <(E-Mail Removed)> wrote in message
news:d430d$400d311a$42a70da1$(E-Mail Removed) ervers.com...
> I hope I'm posting in the right newsgroup.
>
> I am not computer illiterate, but know little about LANs (just basic
stuff),
> and I am trying to set up a small business LAN (actually enhance one that
I
> inheritted). I'll briefly describe what I am trying to do. Any ideas you
> can give me, what to avoid, pointers to good reference material, etc.
would
> be greatly appreciated.
>
> - Existing NT4 Server with 6 clients
> - Want to add a 2003 Small Business Server
> - Want to add a wireless Router (for 3 tablet PCs and 3 Pocket Pcs)
> - Want to add DSL acces to the net
>
> Should the 2003 and NT be part of the same domain? Should I keep them
> separate? At the end of the day, all I want is for the 6 (old) +6
(wireless)
> clients to be able to access both servers, the servers to be able to
access
> each other, and for all clients to have access to the internet.
>
> As I said, any ideas? Any traps to avoid? (like should I have fixed IP
> addresses for each client, or set it up so that the server assigns them?
> Which server should I use to manage that? etc.) Any pointers to good
> reference material?
>
> Thanks,
> Gary
>
>

Thanks for the link. Lots of information there. You mean I have to know
all that to set up a small LAN? Now I see why network people demand the big
bucks <smile>. And here I thought I had a simple situation :-(

I didn't even realize that DNS is something you install. And what did I
say? That I was *not* computer illiterate? Time to re-evaluate
:-( I'll go spend some more time with the URL you gave me...

Thanks,
Gary
--

"Robert L [MS-MVP]" <(E-Mail Removed)> wrote in message
news:OHOs#(E-Mail Removed)...
> yes, they can be the same domain. it is better to install AC and DNS on
the
> 2003. You may also need to install WINS since you have NT.
>
> --
> For more and other information, go to http://www.ChicagoTech.net
>
> Don't send e-mail or reply to me except you need consulting services.
> Posting on MS newsgroup will benefit all readers and you may get more
help.
>
> Robert Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
> http://www.ChicagoTech.net
> This posting is provided "AS IS" with no warranties.
>
> "Gary" <(E-Mail Removed)> wrote in message
> news:d430d$400d311a$42a70da1$(E-Mail Removed) ervers.com...
> > I hope I'm posting in the right newsgroup.
> >
> > I am not computer illiterate, but know little about LANs (just basic
> stuff),
> > and I am trying to set up a small business LAN (actually enhance one
that
> I
> > inheritted). I'll briefly describe what I am trying to do. Any ideas
you
> > can give me, what to avoid, pointers to good reference material, etc.
> would
> > be greatly appreciated.
> >
> > - Existing NT4 Server with 6 clients
> > - Want to add a 2003 Small Business Server
> > - Want to add a wireless Router (for 3 tablet PCs and 3 Pocket Pcs)
> > - Want to add DSL acces to the net
> >
> > Should the 2003 and NT be part of the same domain? Should I keep them
> > separate? At the end of the day, all I want is for the 6 (old) +6
> (wireless)
> > clients to be able to access both servers, the servers to be able to
> access
> > each other, and for all clients to have access to the internet.
> >
> > As I said, any ideas? Any traps to avoid? (like should I have fixed IP
> > addresses for each client, or set it up so that the server assigns them?
> > Which server should I use to manage that? etc.) Any pointers to good
> > reference material?
> >
> > Thanks,
> > Gary
> >
> >
>
>

Well, Robert, I took your advice and set the 2003 as the DC and DNS, and
turned the older NT box just another box on the domain (single domain) -
thanks!. Everything seems to work fine, until the next step which was the
main reason for setting up this network, in the first place. I have a DSL
modem connected to a wireless router which in turn is connected to my main
switch. Using my NT box, I can see and ping the wireless router, but cannot
see the DSL modem's static IP address at all. I spent hours on the phone
both with the DSL service tech and the wireless router tech, and tried all
sorts of things, but no results. DSL works fine if I connect it to a
stand-alone notebook, and I can access the network from wireless nodes, but
can't see the DSL from any node on the network :-(

I wonder if this is even a valid configuration, at this point, although both
DSL and router tech people assure me it is.

Any ideas?

--

"Robert L [MS-MVP]" <(E-Mail Removed)> wrote in message
news:OHOs#(E-Mail Removed)...
> yes, they can be the same domain. it is better to install AC and DNS on
the
> 2003. You may also need to install WINS since you have NT.
>
> --
> For more and other information, go to http://www.ChicagoTech.net
>
> Don't send e-mail or reply to me except you need consulting services.
> Posting on MS newsgroup will benefit all readers and you may get more
help.
>
> Robert Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
> http://www.ChicagoTech.net
> This posting is provided "AS IS" with no warranties.
>
> "Gary" <(E-Mail Removed)> wrote in message
> news:d430d$400d311a$42a70da1$(E-Mail Removed) ervers.com...
> > I hope I'm posting in the right newsgroup.
> >
> > I am not computer illiterate, but know little about LANs (just basic
> stuff),
> > and I am trying to set up a small business LAN (actually enhance one
that
> I
> > inheritted). I'll briefly describe what I am trying to do. Any ideas
you
> > can give me, what to avoid, pointers to good reference material, etc.
> would
> > be greatly appreciated.
> >
> > - Existing NT4 Server with 6 clients
> > - Want to add a 2003 Small Business Server
> > - Want to add a wireless Router (for 3 tablet PCs and 3 Pocket Pcs)
> > - Want to add DSL acces to the net
> >
> > Should the 2003 and NT be part of the same domain? Should I keep them
> > separate? At the end of the day, all I want is for the 6 (old) +6
> (wireless)
> > clients to be able to access both servers, the servers to be able to
> access
> > each other, and for all clients to have access to the internet.
> >
> > As I said, any ideas? Any traps to avoid? (like should I have fixed IP
> > addresses for each client, or set it up so that the server assigns them?
> > Which server should I use to manage that? etc.) Any pointers to good
> > reference material?
> >
> > Thanks,
> > Gary
> >
> >
>
>

"Gary" <(E-Mail Removed)> wrote in message news:<de618$40167361$42a70da1$(E-Mail Removed) servers.com>...
> Well, Robert, I took your advice and set the 2003 as the DC and DNS, and
> turned the older NT box just another box on the domain (single domain) -
> thanks!. Everything seems to work fine, until the next step which was the
> main reason for setting up this network, in the first place. I have a DSL
> modem connected to a wireless router which in turn is connected to my main
> switch. Using my NT box, I can see and ping the wireless router, but cannot
> see the DSL modem's static IP address at all. I spent hours on the phone
> both with the DSL service tech and the wireless router tech, and tried all
> sorts of things, but no results. DSL works fine if I connect it to a
> stand-alone notebook, and I can access the network from wireless nodes, but
> can't see the DSL from any node on the network :-(
>
> I wonder if this is even a valid configuration, at this point, although both
> DSL and router tech people assure me it is.
>
> Any ideas?
>

Sounds like you are making the right connections. Have you tried to
access the DSL model from another box on your network? It may be
something specific to that NT box. Did you make sure that the TCP/IP
settings on the NT network connector are correct?

"Michael" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> "Gary" <(E-Mail Removed)> wrote in message
news:<de618$40167361$42a70da1$(E-Mail Removed) servers.com>...
> > Well, Robert, I took your advice and set the 2003 as the DC and DNS, and
> > turned the older NT box just another box on the domain (single domain) -
> > thanks!. Everything seems to work fine, until the next step which was
the
> > main reason for setting up this network, in the first place. I have a
DSL
> > modem connected to a wireless router which in turn is connected to my
main
> > switch. Using my NT box, I can see and ping the wireless router, but
cannot
> > see the DSL modem's static IP address at all. I spent hours on the
phone
> > both with the DSL service tech and the wireless router tech, and tried
all
> > sorts of things, but no results. DSL works fine if I connect it to a
> > stand-alone notebook, and I can access the network from wireless nodes,
but
> > can't see the DSL from any node on the network :-(
> >
> > I wonder if this is even a valid configuration, at this point, although
both
> > DSL and router tech people assure me it is.
> >
> > Any ideas?
> >
>
> Sounds like you are making the right connections. Have you tried to
> access the DSL model from another box on your network? It may be
> something specific to that NT box. Did you make sure that the TCP/IP
> settings on the NT network connector are correct?

Well, your advice worked, thanks! Accessed it from a different box
(actually all the boxes) and I can communicate to the outside. However, on
the NT box, even when I sign on as admin, I cannot change the TCP/IP
settings for the net adapter, so I can point to the router :-( The Options
tab is grayed out. I wonder if it's some setting, somewhere, that I need to
tweek...