| Cookie Monster 2002-10-21, 1:24 pm |
| I have a number of NT 4.0 servers, and one Windows 2000 server that is a
member server. No AD yet, so basically it's all quite simple - an NT 4.0
Domain, WINS for name resolution, and no DNS. The odd thing about my
network is that all nodes hold a public IP address. Well, soon I'll be
changing things - the network will be private. This place is a round the
clock manufacturing joint so bringing things down for redesigning of the LAN
is not really feasible. So what I did was take my Win2K server and make it
DHCP server, and with a second NIC I enabled internet sharing (NAT), and
because of this I can now add clients to the LAN that have private IP
addresses. Connectivity exists! One problem though. My Win2K Pro machines
(clients) are now configured to get an IP address from the DHCP server, and
they do. One thing to note. I now have to networks - the pre-existing
network with the public ip's, and the new network that assigns private IP's
via DHCP. So what allows commuication between the two? The answer is
Internet Connection Sharing, ICS, or NAT, whatever. My servers all hold
public IP addreses and so my client machines are no longer authenticating to
the domain. They allow you in, because Win2K seems to store the last
successful password, but then when you try to access a network resource
llike a folder, well it then prompts you for user name, domain, and
password, and upon reception of those - it works. If only I could get the
private network machines to authenticate once again. Thanks for listening,
and thanks even more if you have iput.
|