• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2987
  • Last Modified:

\\computer name\ is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to out if you have access permissions.

\\computer name\ is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to out if you have access permissions.
Multiple connections to a server or shared resource 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..

Above error occurrs when XP PC#1 authenticated with Domain#1 attempts to access/login to XP PC#2 in Domain#2. There is currently no trust between the domains. The user credientials are all correct on all domains.
Does anyone know what would be causing and/or a workaround.
Thanks, cj
0
cjsling
Asked:
cjsling
  • 3
  • 2
1 Solution
 
Pete LongConsultantCommented:
XP is limited to 10 concurrent connections - is this your problem?
0
 
Pete LongConsultantCommented:
what happens if you

net use h: \\PC2\c$ password /user:pc2\administrator

using PC2's LOCAL administrators password
0
 
cjslingAuthor Commented:
This could not be the problem. I wanted to simplify the problem by using an XP box. The same message occurrs for Windows 2003 server.
This is my response:

system error 67 has occurred.
The network name cannont be found

0
 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

 
oBdACommented:
The problem here seems to be that you already have a connection to the other machine open, using a different account than the one you're trying to use right now.
Open a command prompt and run "net use" to display all connections that are opened at the moment; disconnect the one(s) to the target PC.
Or use the workaround, and map/access using the IP address.
0
 
Pete LongConsultantCommented:
g'day oBdA :)

>>The network name cannont be found

can you ping PC#2 from PC#1?

0
 
cjslingAuthor Commented:
That was IT! The login script was mapping to the server. I disconnected the connection and logged in successfully.

Thank you!!
0

Featured Post

What Security Threats Are We Predicting for 2018?

Cryptocurrency, IoT botnets, MFA, and more! Hackers are already planning their next big attacks for 2018. Learn what you might face, and how to defend against it with our 2018 security predictions.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now