G
Glenn
Hello,
I have replaced my NT4 Server box with a new hardware and Windows 2000
Server (SP3). I have a about 18 client machines running XP Pro/2000 Pro/NT
4 WS/Win 98.
A peculiar thing is happening. Our domain is called "twin" and all the
clients have various mapping to other clients within our "twin" domain. So
the problem is this;
Frequently the WinXP/Win2K clients loose the ability to browse the "twin"
network through the explorer (My network places/Microsoft Windows
Network/Twin) interface- they get "twin not accessible....", however, they
can still utilize any pre-existing drive mappings, including access to the
server and/or client machines.
If I go through the 4 steps of "ipconfig" using the following parameters
---> /release /flushdns /renew /registerdns <---
then I get access again. But at some point, it gets locked out again.
(I am not sure if this occurs on NT/98 as those machines are not really used
day to day)
Any ideas/suggestions?
Thanks in advance,
Glenn
I have replaced my NT4 Server box with a new hardware and Windows 2000
Server (SP3). I have a about 18 client machines running XP Pro/2000 Pro/NT
4 WS/Win 98.
A peculiar thing is happening. Our domain is called "twin" and all the
clients have various mapping to other clients within our "twin" domain. So
the problem is this;
Frequently the WinXP/Win2K clients loose the ability to browse the "twin"
network through the explorer (My network places/Microsoft Windows
Network/Twin) interface- they get "twin not accessible....", however, they
can still utilize any pre-existing drive mappings, including access to the
server and/or client machines.
If I go through the 4 steps of "ipconfig" using the following parameters
---> /release /flushdns /renew /registerdns <---
then I get access again. But at some point, it gets locked out again.
(I am not sure if this occurs on NT/98 as those machines are not really used
day to day)
Any ideas/suggestions?
Thanks in advance,
Glenn