Network connection weirdness between NT4, 2000, over router.
Hey there, I'm having some problems with a server that I just built. Here's the deal: I work in a hospital that has about 6 remote locations. The main location has about 30 NT/2000 servers, but it is still a Windows NT4 Domain.
Hey there,
I'm having some problems with a server that I just built.
Here's the deal:
I work in a hospital that has about 6 remote locations. The main location has about 30 NT/2000 servers, but it is still a Windows NT4 Domain.
There was a NT4 BDC at a very small remote location. This box did logins for the 20 or so people there, and also WINS and DHCP was running on this box. People mainly used this box for home drives and a shared drive.
Today I took out a Windows 2000 server that I built over the last week and went to install it. It fired up and I logged onto the network with no problems. I however didn't have WINS running on this new server, nor was it a BDC. I later installed WINS and it also has DHCP running. Since we currently cannot afford to go to Active Directory, we were just planning on having them authenticate over the wire to the main building but get their IP addresses from the new Windows 2000 Server (we have a half of a T1 between the two).
That seemed to be working fine. A few boxes and also my laptop got IP's from the new server.
Here's where it gets weird....
There is a router at this remote location and they are on their own subnet. I go into My Network Places on the new server and I cannot see any Servers except the one new one I'm on. I however can go to a run box and type \\servername and get into other network servers like that...
I can also ping boxes accross the wire......either by IP or NetBios name.
I go to some of the workstations and try to connect to the new Windows 2000 Server shares and I get a message that says that no server was available to authenticate me. I can however get to any of the servers on the other side of the router with no problem.
It seems to me that the new Windows 2000 server I set up at the remote location is looking to a domain controller across the wire to see if the connecting users have permissions etc..... But it's like it can't find one to authenticate....
I'm so lost and beating my head against the wall here...
I haven't changed anything except the server, and I have successfully ( I think) done Push/Pulls between other WINS servers back at the main location.
Am I forgetting something simple....?
Does Win2k have some problem with WinNT4......?
-------------------
I know this is a long question. I appreciate you very much if you've read this far. Thanks for reading If you know anything.......please let me know
Have a great day...
-Dude
I'm having some problems with a server that I just built.
Here's the deal:
I work in a hospital that has about 6 remote locations. The main location has about 30 NT/2000 servers, but it is still a Windows NT4 Domain.
There was a NT4 BDC at a very small remote location. This box did logins for the 20 or so people there, and also WINS and DHCP was running on this box. People mainly used this box for home drives and a shared drive.
Today I took out a Windows 2000 server that I built over the last week and went to install it. It fired up and I logged onto the network with no problems. I however didn't have WINS running on this new server, nor was it a BDC. I later installed WINS and it also has DHCP running. Since we currently cannot afford to go to Active Directory, we were just planning on having them authenticate over the wire to the main building but get their IP addresses from the new Windows 2000 Server (we have a half of a T1 between the two).
That seemed to be working fine. A few boxes and also my laptop got IP's from the new server.
Here's where it gets weird....
There is a router at this remote location and they are on their own subnet. I go into My Network Places on the new server and I cannot see any Servers except the one new one I'm on. I however can go to a run box and type \\servername and get into other network servers like that...
I can also ping boxes accross the wire......either by IP or NetBios name.
I go to some of the workstations and try to connect to the new Windows 2000 Server shares and I get a message that says that no server was available to authenticate me. I can however get to any of the servers on the other side of the router with no problem.
It seems to me that the new Windows 2000 server I set up at the remote location is looking to a domain controller across the wire to see if the connecting users have permissions etc..... But it's like it can't find one to authenticate....
I'm so lost and beating my head against the wall here...
I haven't changed anything except the server, and I have successfully ( I think) done Push/Pulls between other WINS servers back at the main location.
Am I forgetting something simple....?
Does Win2k have some problem with WinNT4......?
-------------------
I know this is a long question. I appreciate you very much if you've read this far. Thanks for reading If you know anything.......please let me know
Have a great day...
-Dude
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Yo,
I fixed it
It was, of course, something trivial.
I had to set the WINS address on the server to point to the MAIN hospital to get this thing back on the domain....and then i started WINS on the server......then pointed the WINS address on the server to itself.
After that I changed the DHCP scope so that it would hand out the WINS address of itself as primary and the main hospital secondary. Everything works like a champ now
Thanks for all the folks that looked anyway. I know this was a tough one
I fixed it
It was, of course, something trivial.
I had to set the WINS address on the server to point to the MAIN hospital to get this thing back on the domain....and then i started WINS on the server......then pointed the WINS address on the server to itself.
After that I changed the DHCP scope so that it would hand out the WINS address of itself as primary and the main hospital secondary. Everything works like a champ now
Thanks for all the folks that looked anyway. I know this was a tough one
