Re: File Server cannot connect to shared client drive
- From: "Mark J. Wallin" <mjwallin@xxxxxxxxxx>
- Date: Fri, 02 Feb 2007 16:37:24 -0500
Herb Martin wrote:
"Mark J. Wallin, Ph.D." <mjwallin@xxxxxxxxxx> wrote in message
news:OcgQZ6vRHHA.4744@xxxxxxxxxxxxxxxxxxxxxxx
I have a small network of 15 PC's currently configured as a Workgroup.
The clients are Windows 2000 and the Server machine is running W2003 (R2).
The problem I am having is that I cannot access the shared drive on one
machine from the Server using the Administrator account. There is no
problem accessing any of the other clients.
Most likely reasons:
1) Firewall on client
There is no firewall on the the client; there is an anti-virus program,
however, which is also on the other clients. The network firewall is in
the cable modem/router.
2) Using admin account from domain but machine is not "in the domain"
There is no domain. It was removed due to major a crash and the need to
get the users back online ASAP. All workstations were cleared of domain
references as far as could be done without reinstalling the O/S. The
domain suffix in the machine identifier was cleared.
3) Nothing is shared (or using wrong share)
As indicated, the problem client is accessible from all other PC's in
the workgroup except the server.
The clients are all set up
with an administrative account that matches the Server account name and
password.
Are you in a workgroup and depending on the accounts to "match" (ie.
username and password)?
Yes.
Try it with an explicit "net use" command and provide the password; try
it from the SAME machine (to try to eliminate firewall), try it by IP
address etc.
net use * \\Machine\ShareName * /user:MachineName\Username
net use * \\Machine.IP.Addr.ess\ShareName *
/user:MachineName\Username
The results were:
NET USE * \\<client>\<clientShare> /user:MachineName\username, I get the
error:
"Sytem error 1219 has occurred.
Multiple connections to a server or shared resources by the same user,
using more than one user name, are not allowed. Disconnect all previous
connections to the server or shared resource and try again."
With NET USE \\Machine.IP.Addr.ess\Sharename, the client gets connected
as the Z: drive.
.
- Follow-Ups:
- Re: File Server cannot connect to shared client drive
- From: Herb Martin
- Re: File Server cannot connect to shared client drive
- 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
- File Server cannot connect to shared client drive
- Prev by Date: Windows cannot connect to the domain error. Virtual Server or other cause?
- Next by Date: Re: Windows cannot connect to the domain error. Virtual Server or other cause?
- Previous by thread: Re: File Server cannot connect to shared client drive
- Next by thread: Re: File Server cannot connect to shared client drive
- Index(es):
Relevant Pages
|