B
barbie gee
all clients are XP Pro, patched currently but NOT SP2.
\\Server_X is Windows 2000, in an AD mixed-mode domain, we'll call
BAD_DOMAIN.
Everyone was able to connect to a share until last week, when we had a
massive power outage on campus. Now, no one can connect. We get
errors saying that "the mapped network drive could not be created
because the following error has occurred: The specified network name
is no loger available."
PING works ok. We can ping either by IP address, FQDN, or host name.
Net View /domain:bad_domain shows \\server_x
net use q: \\server_x\share, however, fails with "system error 64 has
occurrred. The specified network name is no longer available".
Yes, I've done a "net use * /delete"
From \\server_x, we can reach shares on other trusting/trusted
domains. Within the BAD_DOMAIN, those users, except for one, can all
access \\server_x\share.
I'm totally at my wits end.
ANY IDEAS???
\\Server_X is Windows 2000, in an AD mixed-mode domain, we'll call
BAD_DOMAIN.
Everyone was able to connect to a share until last week, when we had a
massive power outage on campus. Now, no one can connect. We get
errors saying that "the mapped network drive could not be created
because the following error has occurred: The specified network name
is no loger available."
PING works ok. We can ping either by IP address, FQDN, or host name.
Net View /domain:bad_domain shows \\server_x
net use q: \\server_x\share, however, fails with "system error 64 has
occurrred. The specified network name is no longer available".
Yes, I've done a "net use * /delete"
From \\server_x, we can reach shares on other trusting/trusted
domains. Within the BAD_DOMAIN, those users, except for one, can all
access \\server_x\share.
I'm totally at my wits end.
ANY IDEAS???