R
Roman
I have a WIN2K Server PDC with SP3 on a network with 10 computers, all
running XP Pro. My Internet connection is a DSL with a Netgear
RP614v2 Router that serves as a DHCP Server, NAT firewall and port
forwarding.
Here's the problem: If I log onto the W2K server after restarting it,
the computers including the server, are no longer able to access any
of the WAN addresses through HTTP or other protocols (such as mail),
until I reboot the W2K server. If I don't log on to the W2K server
after reboot, everything works perfectly.
WAN connection is not the problem, because I can still ping any
address even after logging onto the server. I removed port forwarding
and it didn't make any difference, either. A clue might be the fact
that the incoming connections (such as HTTP and mail protocols) work
at all times, even with ports forwarded to the W2K Server.
Any idea what the log in process might be starting that somehow ruins
everything?
running XP Pro. My Internet connection is a DSL with a Netgear
RP614v2 Router that serves as a DHCP Server, NAT firewall and port
forwarding.
Here's the problem: If I log onto the W2K server after restarting it,
the computers including the server, are no longer able to access any
of the WAN addresses through HTTP or other protocols (such as mail),
until I reboot the W2K server. If I don't log on to the W2K server
after reboot, everything works perfectly.
WAN connection is not the problem, because I can still ping any
address even after logging onto the server. I removed port forwarding
and it didn't make any difference, either. A clue might be the fact
that the incoming connections (such as HTTP and mail protocols) work
at all times, even with ports forwarded to the W2K Server.
Any idea what the log in process might be starting that somehow ruins
everything?