|
Question : Long Delay Opening Files In Windows Explorer, Phantom IP Addresses
|
|
This problem ocurrs on a single workstation on a domain that has had the domain controller recently replaced with a new box at a new IP. All files in all programs, local or network drives take an exceptionally long time to open when double-clicked in explorer, 50-80 seconds. Once open the files respond normally.
The symtoms and troubleshooting are almost exactly like this previous issue: http://www.experts-exchange.com/Networking/Misc/Q_21945247.html
I have narrowed my problem down to a phantom IP address that is the old domain controller. Here is the output from the netstat -a command: Proto Local Address Foreign Address State TCP bkmodesktop7:epmap bkmodesktop7:0 LISTENING TCP bkmodesktop7:microsoft-ds bkmodesktop7:0 LISTENING TCP bkmodesktop7:1027 bkmodesktop7:0 LISTENING TCP bkmodesktop7:4664 bkmodesktop7:0 LISTENING TCP bkmodesktop7:netbios-ssn bkmodesktop7:0 LISTENING TCP bkmodesktop7:1072 p1w27.geo.scd.yahoo.com:http TIME_WAIT TCP bkmodesktop7:1083 72.5.124.55:http CLOSE_WAIT TCP bkmodesktop7:1084 128.242.186.218:http ESTABLISHED TCP bkmodesktop7:1086 128.242.186.218:http ESTABLISHED TCP bkmodesktop7:1087 192.168.1.202:microsoft-ds SYN_SENT UDP bkmodesktop7:microsoft-ds *:* UDP bkmodesktop7:isakmp *:* UDP bkmodesktop7:1025 *:* UDP bkmodesktop7:1048 *:* UDP bkmodesktop7:4500 *:* UDP bkmodesktop7:ntp *:* UDP bkmodesktop7:1900 *:* UDP bkmodesktop7:ntp *:* UDP bkmodesktop7:netbios-ns *:* UDP bkmodesktop7:netbios-dgm *:* UDP bkmodesktop7:1900 *:*
192.168.1.202 is the old server. I have scoured the registry for any entry related to this IP address, drive mappings or explorer settings. I have disjoined the PC from the domain and rejoined. I can't get at it and really don't want to reformat this user's PC. Any ideas would be greatly appreciated.
|
Answer : Long Delay Opening Files In Windows Explorer, Phantom IP Addresses
|
|
Make sure the old server has been removed from active directory and from your DNS server.
I assume you checked the network settings of the workstation to make sure it wasn't listed as one of the DNS servers?
|
|
|
|