Mapped drives connected but not accessible
I have a long-time setup for backups where each computer to be backed up has a particular folder which is mapped onto the backup computer.
Recently, the backups didn't run because, it appears, the mapped drives weren't "there".
But they were and they weren't showing as disconnected.
I opened them in Windows just fine.
After that, the backups would run normally.
I can't have this happening and I can't figure out what was causing this strange behavior. This has been working for years!
Recently, the backups didn't run because, it appears, the mapped drives weren't "there".
But they were and they weren't showing as disconnected.
I opened them in Windows just fine.
After that, the backups would run normally.
I can't have this happening and I can't figure out what was causing this strange behavior. This has been working for years!
wolfcamel
check the log on the backup computer - if it is a windows PC not a server you may have exceeded the number of allowable connections
During that there could be possible network fluctuations. in destination or source end....
if you face the same issue again then please check the net connectivity....
if you face the same issue again then please check the net connectivity....
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
- It's not the number of connections.
- I've used the NET USE command for things like this in the past. But this one has been stable for years so I'd like to avoid that. May be forced to.
-
I see a large number of errors extending over this whole week that say:
"The server {5A5AA0AA-...........} did not register with DCOM within the required timeout."
- I've used the NET USE command for things like this in the past. But this one has been stable for years so I'd like to avoid that. May be forced to.
-
I see a large number of errors extending over this whole week that say:
"The server {5A5AA0AA-...........} did not register with DCOM within the required timeout."
ASKER
Does the error reveal anything?
I implemented the NET USE command.
I also did this:
NET CONFIG SERVER AUTODISCONNECT:-1
but now we get errors / non-connects / with "too many users".
I posted another question related to this.
Await more info re: the errors seen as above.
I implemented the NET USE command.
I also did this:
NET CONFIG SERVER AUTODISCONNECT:-1
but now we get errors / non-connects / with "too many users".
I posted another question related to this.
Await more info re: the errors seen as above.
ASKER
Does anyone understand the error:
"The server {5A5AA0AA-...........} did not register with DCOM within the required timeout."
It seems to have been generated quite often at the same time this problem started.
"The server {5A5AA0AA-...........} did not register with DCOM within the required timeout."
It seems to have been generated quite often at the same time this problem started.
On September 28th, 2011:
http://support.microsoft.com/kb/909444
You may experience various problems after you install the Microsoft Security Bulletin MS05-051 for COM+ and MS DTC
http://support.microsoft.com/kb/909444