C
Chris
This has beaten to death everywhere, but I still have the
problem.
I have a mixed network of XP Pro and Win98, with WIN 2K
servers (SP4), and I run AD, WINS, etc....and I have made
sure the everything in DHCP is correct....according to
other posts from Marina.
The 98 clients are fine, the XP clients can take up to 5
mins or more to access a share on one of the 2K servers.
Windows Explorer seems to hang when you first open the
share...5mins...everything is fine. Strangely, if I end the
windows explorer process during this blind period, and
restart explorer...the share instantly appears.
I can access the share numerous times after the initial
with no delay. After 20 mins, something times out and I
have to repeat the wait all over again.
Here is what I found yesterday, on a cold boot, and before
I try to access the share through explorer, I tried to
access the share trough the cmd prompt, aka
\\192.168.10.1\company To my disbelief, I was able to
browse all of the share's contents instantly. What the heck?
I have tried every registry fix, DNS Fix, SMB fix, and all
other MS hotfixs, to no avail.
Any other idea's floating around? This was working fine
about 3 months ago. I'm sure it was a MS Hotfix/Security
fix that broke everything.
problem.
I have a mixed network of XP Pro and Win98, with WIN 2K
servers (SP4), and I run AD, WINS, etc....and I have made
sure the everything in DHCP is correct....according to
other posts from Marina.
The 98 clients are fine, the XP clients can take up to 5
mins or more to access a share on one of the 2K servers.
Windows Explorer seems to hang when you first open the
share...5mins...everything is fine. Strangely, if I end the
windows explorer process during this blind period, and
restart explorer...the share instantly appears.
I can access the share numerous times after the initial
with no delay. After 20 mins, something times out and I
have to repeat the wait all over again.
Here is what I found yesterday, on a cold boot, and before
I try to access the share through explorer, I tried to
access the share trough the cmd prompt, aka
\\192.168.10.1\company To my disbelief, I was able to
browse all of the share's contents instantly. What the heck?
I have tried every registry fix, DNS Fix, SMB fix, and all
other MS hotfixs, to no avail.
Any other idea's floating around? This was working fine
about 3 months ago. I'm sure it was a MS Hotfix/Security
fix that broke everything.