Re: File Server cannot connect to shared client drive
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Fri, 2 Feb 2007 18:30:56 -0600
"Mark J. Wallin" <mjwallin@xxxxxxxxxx> wrote in message
news:%23Jzb$nyRHHA.4632@xxxxxxxxxxxxxxxxxxxxxxx
Herb Martin wrote:
Then run:
Net Use * /d
...to delete all connections to shares and try again.
It acts as if you have another connection to the same machine.
With NET USE \\Machine.IP.Addr.ess\Sharename, the client gets connected
as the Z: drive.
Odd, if the Machine is the SAME machne (name and IP) you should have
gotten
the same error.
Thanks, that seemed to work. I can't imagine how it got into that
state. Too bad windows doesn't let you see what is going on inside.
Well, it typically does that if you just know what tool to use and carefully
read the error messages and built-in help (not always, but more often than
most people realize.)
In this case it said "Sytem error 1219 has occurred. Multiple connections to
a server or shared resources by the same user" and the command:
net use
....would have shown you that; as "net use * /d" removed them all without us
bothering to first look and confirm the error message was correct.
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)
.
- References:
- File Server cannot connect to shared client drive
- From: Mark J. Wallin, Ph.D.
- Re: File Server cannot connect to shared client drive
- From: Herb Martin
- Re: File Server cannot connect to shared client drive
- From: Mark J. Wallin
- Re: File Server cannot connect to shared client drive
- From: Herb Martin
- Re: File Server cannot connect to shared client drive
- From: Mark J. Wallin
- File Server cannot connect to shared client drive
- Prev by Date: Re: File Server cannot connect to shared client drive
- Next by Date: Re: 2003 DST patch without SP1???
- Previous by thread: Re: File Server cannot connect to shared client drive
- Next by thread: shadow copy and backup
- Index(es):
Relevant Pages
|