Now here's an oddity (Win2K)
-
I finally got around to connecting my old Win2K Pro PC to the Win2K Server today. I added the old pc to the Active Directory, made a Domain User account for my old logon, hooked them both into the switch and enabled the interfaces. NAT is installed on the external interface, and the server internal interface is configured at 192.168.x.y per the online instructions. I also added a subnet for the internal network to the Active Directory. The curious part is that when I attempt to join the domain from the client, it reports that the network path couldn't be found, yet I can ping the server without trouble! Even more surprising is that from the client, with no physical connection to the outside world except thru the server, I can surf the 'net without trouble! Any ideas as to where I should look for the trouble?
-
I finally got around to connecting my old Win2K Pro PC to the Win2K Server today. I added the old pc to the Active Directory, made a Domain User account for my old logon, hooked them both into the switch and enabled the interfaces. NAT is installed on the external interface, and the server internal interface is configured at 192.168.x.y per the online instructions. I also added a subnet for the internal network to the Active Directory. The curious part is that when I attempt to join the domain from the client, it reports that the network path couldn't be found, yet I can ping the server without trouble! Even more surprising is that from the client, with no physical connection to the outside world except thru the server, I can surf the 'net without trouble! Any ideas as to where I should look for the trouble?
I have experienced this before, but after I let the workstation stay connected to the network for a few hours I was able to join the domain. I have no good idea why it took so long though. Did you ever get it to work? Regards, -- Dana Holt Xenos Software
-
I have experienced this before, but after I let the workstation stay connected to the network for a few hours I was able to join the domain. I have no good idea why it took so long though. Did you ever get it to work? Regards, -- Dana Holt Xenos Software
I had given up for a while, but your reply got me to tinkering with it again. Using NAT on the server is supposed to act as a DHCP server to the local clients, but that's not happening. So I hardwired the IP settings on the client. I also forgot that I had ZoneAlarm onthe old PC, so I disabled it. The wizard for joining a domain still doesn't work (can't find the domain), but the second option to change the domain worked! I can now view the network (but not the shares on the server - more work to be done there), and access the client from the server. Unfortunately, whenever the local network is enabled on the server, I can no longer find anything on the web - I get a lot of activity on the local net but it never tries the external interface. Back to the drawing board:-D
-
I had given up for a while, but your reply got me to tinkering with it again. Using NAT on the server is supposed to act as a DHCP server to the local clients, but that's not happening. So I hardwired the IP settings on the client. I also forgot that I had ZoneAlarm onthe old PC, so I disabled it. The wizard for joining a domain still doesn't work (can't find the domain), but the second option to change the domain worked! I can now view the network (but not the shares on the server - more work to be done there), and access the client from the server. Unfortunately, whenever the local network is enabled on the server, I can no longer find anything on the web - I get a lot of activity on the local net but it never tries the external interface. Back to the drawing board:-D
Roger Wright wrote: Using NAT on the server is supposed to act as a DHCP server to the local clients, but that's not happening. NAT is unrelated to DHCP, so you will have to configure DHCP as another step. That is unless you are using some kind of wizard that does both at the same time behind the scenes. Roger Wright wrote: Unfortunately, whenever the local network is enabled on the server, I can no longer find anything on the web - I get a lot of activity on the local net but it never tries the external interface. Back to the drawing board You should try to do a tracert to a web address to see where the traffic is going. Your routing table should contain a default route that goes out your external (internet) NIC. This will let all addresses not on your internal network go out to the net. You can use "route print" to see the routing table and "route /?" to get available routing commands. Isn't networking fun? :eek: Good luck! -- Dana Holt Xenos Software
-
Roger Wright wrote: Using NAT on the server is supposed to act as a DHCP server to the local clients, but that's not happening. NAT is unrelated to DHCP, so you will have to configure DHCP as another step. That is unless you are using some kind of wizard that does both at the same time behind the scenes. Roger Wright wrote: Unfortunately, whenever the local network is enabled on the server, I can no longer find anything on the web - I get a lot of activity on the local net but it never tries the external interface. Back to the drawing board You should try to do a tracert to a web address to see where the traffic is going. Your routing table should contain a default route that goes out your external (internet) NIC. This will let all addresses not on your internal network go out to the net. You can use "route print" to see the routing table and "route /?" to get available routing commands. Isn't networking fun? :eek: Good luck! -- Dana Holt Xenos Software
Dana Holt wrote: That is unless you are using some kind of wizard that does both at the same time behind the scenes. According to the Win2K documentation, that's exactly what NAT is supposed to do. I'm ignoring it for now, since the static settings aren't all that tough to maintain (one client). Dana Holt wrote: You should try to do a tracert to a web address to see where the traffic is going. No need. Like your experience, now that it's been running a while, it's learning where to look as it builds a routing table:-D Dana Holt wrote: Isn't networking fun? Actually, yes it is! That's why I've been doing it for 7 years. But this is my first Win2K server, and as with all networking products, the docs are misleading and often plain wrong. Stumbling around in the dark a lot is part and parcel of networking... :laugh: Thanks for your suggestions!
-
Dana Holt wrote: That is unless you are using some kind of wizard that does both at the same time behind the scenes. According to the Win2K documentation, that's exactly what NAT is supposed to do. I'm ignoring it for now, since the static settings aren't all that tough to maintain (one client). Dana Holt wrote: You should try to do a tracert to a web address to see where the traffic is going. No need. Like your experience, now that it's been running a while, it's learning where to look as it builds a routing table:-D Dana Holt wrote: Isn't networking fun? Actually, yes it is! That's why I've been doing it for 7 years. But this is my first Win2K server, and as with all networking products, the docs are misleading and often plain wrong. Stumbling around in the dark a lot is part and parcel of networking... :laugh: Thanks for your suggestions!
Roger Wright wrote: Actually, yes it is! That's why I've been doing it for 7 years. But this is my first Win2K server, and as with all networking products, the docs are misleading and often plain wrong. Stumbling around in the dark a lot is part and parcel of networking... Yeah, I used to stumble around in the dark with networking, but now I stumble around in the dark with programming! :laugh: Roger Wright wrote: Thanks for your suggestions! You're welcome. -- Dana Holt Xenos Software