One more ? about networks w/NT server

After getting this router and internet service set up, I have been doing a
bit of thinking about my company's NT network setup.

First, each computer has a static IP address that was set up on it way back
when the network was first installed. This is set-up through TCP/IP
properties. That being said, can I figure that the server is not really
handling DHCP? When we check the server, we only find the clients listed
by name, not IP Address. Any other computers not on the network (and even
one that was that, for some reason could no longer access the network) had
to also have static IP address information set up on them manually along
with gateway and DNS configuration. I think the computer that could no
longer access the network could not do so, because for some reason, that
manual setting for IP address was no longer on it. I had to manually enter
info in order to get it to work with the router and perhaps it will now
work with the server, I haven't checked it yet.

Now, does that mean, I could enable the DHCP on the router and allow the
router to assign the IP addresses? Does the NT server not care what IP
address the computers have (as long as they're within the network range)
and does it only care about the log-in name? So, if the router took over
the DHCP duties would that be a better option than having the IP addresses
set manually on each computer?

Also, there is a DNS setting in the DNS configuration on each computer.
I'm not sure what that setting relates to, do you think if could be for the
ISP they were using and should it be changed to the new ISP's DNS
information? I'm surprised, however, that the computers get online through
the new ISP if that information needs to be changed.

Forgive all these questions of a person fairly inexperienced regarding
networks. I have worked with simple file and printer sharing (peer-to-peer
types) for many years but have not worked in an NT server environment
before. Thanks so much for putting up with my learning process.

Patty

A bit more info, the DNS configuraton points to an old system they had
called an Itel InBusiness Internet Station 56K. We changed the DNS
settings on one of the computers to our current ISP's DNS settings and it
works fine. So, is this setting pretty much irrelevant in the grand scheme
of things? Why would it work with a DNS number that really hasn't pointed
to anything in years? Thanks again.

Patty

On Fri, 15 Apr 2005 10:37:19 -0400, Patty wrote:

>
> Also, there is a DNS setting in the DNS configuration on each computer.
> I'm not sure what that setting relates to, do you think if could be for the
> ISP they were using and should it be changed to the new ISP's DNS
> information? I'm surprised, however, that the computers get online through
> the new ISP if that information needs to be changed.

> Patty

we don't know how many computer you have in the LAN and if you have domain ro workgroup. after read your post, I think you should install DHCP and DNS on the NT server. For more and other information, go to http://howtonetworking.com.

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.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
I recommend Brinkster for web hosting!

"Patty" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
After getting this router and internet service set up, I have been doing a
bit of thinking about my company's NT network setup.

First, each computer has a static IP address that was set up on it way back
when the network was first installed. This is set-up through TCP/IP
properties. That being said, can I figure that the server is not really
handling DHCP? When we check the server, we only find the clients listed
by name, not IP Address. Any other computers not on the network (and even
one that was that, for some reason could no longer access the network) had
to also have static IP address information set up on them manually along
with gateway and DNS configuration. I think the computer that could no
longer access the network could not do so, because for some reason, that
manual setting for IP address was no longer on it. I had to manually enter
info in order to get it to work with the router and perhaps it will now
work with the server, I haven't checked it yet.

Now, does that mean, I could enable the DHCP on the router and allow the
router to assign the IP addresses? Does the NT server not care what IP
address the computers have (as long as they're within the network range)
and does it only care about the log-in name? So, if the router took over
the DHCP duties would that be a better option than having the IP addresses
set manually on each computer?

Also, there is a DNS setting in the DNS configuration on each computer.
I'm not sure what that setting relates to, do you think if could be for the
ISP they were using and should it be changed to the new ISP's DNS
information? I'm surprised, however, that the computers get online through
the new ISP if that information needs to be changed.

Forgive all these questions of a person fairly inexperienced regarding
networks. I have worked with simple file and printer sharing (peer-to-peer
types) for many years but have not worked in an NT server environment
before. Thanks so much for putting up with my learning process.

Patty

On Fri, 15 Apr 2005 10:23:55 -0600, Robert L [MS-MVP] wrote:

> we don't know how many computer you have in the LAN and if you have domain ro workgroup. after read your post, I think you should install DHCP and DNS on the NT server. For more and other information, go to http://howtonetworking.com.
>
> 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.
>
> Bob Lin, MS-MVP, MCSE & CNE

Three workstations. Can possibly have more, but only three right now.
Originally had more than that at one time when the network was set up.
Domain, I believe.

Sorry, I'm not sure where to look on the page you referenced on how to
install DHCP and DNS on the server.

Patty

Client machines can use DHCP fine. Never do that with Servers,...leave
Servers statically assigned.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

"Patty" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> After getting this router and internet service set up, I have been doing a
> bit of thinking about my company's NT network setup.
>
> First, each computer has a static IP address that was set up on it way
back
> when the network was first installed. This is set-up through TCP/IP
> properties. That being said, can I figure that the server is not really
> handling DHCP? When we check the server, we only find the clients listed
> by name, not IP Address. Any other computers not on the network (and even
> one that was that, for some reason could no longer access the network) had
> to also have static IP address information set up on them manually along
> with gateway and DNS configuration. I think the computer that could no
> longer access the network could not do so, because for some reason, that
> manual setting for IP address was no longer on it. I had to manually
enter
> info in order to get it to work with the router and perhaps it will now
> work with the server, I haven't checked it yet.
>
> Now, does that mean, I could enable the DHCP on the router and allow the
> router to assign the IP addresses? Does the NT server not care what IP
> address the computers have (as long as they're within the network range)
> and does it only care about the log-in name? So, if the router took over
> the DHCP duties would that be a better option than having the IP addresses
> set manually on each computer?
>
> Also, there is a DNS setting in the DNS configuration on each computer.
> I'm not sure what that setting relates to, do you think if could be for
the
> ISP they were using and should it be changed to the new ISP's DNS
> information? I'm surprised, however, that the computers get online
through
> the new ISP if that information needs to be changed.
>
> Forgive all these questions of a person fairly inexperienced regarding
> networks. I have worked with simple file and printer sharing
(peer-to-peer
> types) for many years but have not worked in an NT server environment
> before. Thanks so much for putting up with my learning process.
>
> Patty

On Fri, 15 Apr 2005 11:43:47 -0500, Phillip Windell wrote:

> Client machines can use DHCP fine. Never do that with Servers,...leave
> Servers statically assigned.

So, I could let the router assign IP addresses to the clients, but the
server should be set statically through its TCP/IP settings?

Patty

Yes. Servers should always be static. Servers need to "stand on their own
two feet" and not be dependent on a DHCP server to function. Even if you
uses Reservation in DHCP to get the same IP# everytime, they would still be
dependent on DHCP and that is bad.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Patty" <(E-Mail Removed)> wrote in message
news:1kw5g17fixlp9$.(E-Mail Removed).. .
> On Fri, 15 Apr 2005 11:43:47 -0500, Phillip Windell wrote:
>
> > Client machines can use DHCP fine. Never do that with Servers,...leave
> > Servers statically assigned.
>
> So, I could let the router assign IP addresses to the clients, but the
> server should be set statically through its TCP/IP settings?
>
> Patty

On Fri, 15 Apr 2005 13:05:28 -0500, Phillip Windell wrote:

> Yes. Servers should always be static. Servers need to "stand on their own
> two feet" and not be dependent on a DHCP server to function. Even if you
> uses Reservation in DHCP to get the same IP# everytime, they would still be
> dependent on DHCP and that is bad.

So, perhaps I should just leave everything like it is. It all works, I was
only concerned about the DNS configuration, which doesn't seem to have any
impact on the LAN or internet service.

Patty

DNS has everything to do with the LAN. Domians can't function without
properly setup DNS.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

"Patty" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On Fri, 15 Apr 2005 13:05:28 -0500, Phillip Windell wrote:
>
> > Yes. Servers should always be static. Servers need to "stand on their
own
> > two feet" and not be dependent on a DHCP server to function. Even if you
> > uses Reservation in DHCP to get the same IP# everytime, they would still
be
> > dependent on DHCP and that is bad.
>
> So, perhaps I should just leave everything like it is. It all works, I
was
> only concerned about the DNS configuration, which doesn't seem to have any
> impact on the LAN or internet service.
>
> Patty