Cannot connect to a network share
Hello,
I have a user who is having difficulty mapping to a network share. The permissions are correct as I can map to the network drive using his credentials with no issues on a different computer.
This seems to be isolated to the machine and I'm not exactly sure where to look. This doesn't seem to be a networking issue as much as it seems to be a windows 7 holding on to incorrect credentials somewhere on the machine. When I try to map a drive from this particular laptop, it just asks for credentials for the share over and over again as if it's an incorrect password. However, doing it from my laptop, no issues with the same user account.
The user is able to ping the server he is trying to connect to and also do a successful tracert to it. There doesn't seem to be any loss of communication.
Any ideas?
I have a user who is having difficulty mapping to a network share. The permissions are correct as I can map to the network drive using his credentials with no issues on a different computer.
This seems to be isolated to the machine and I'm not exactly sure where to look. This doesn't seem to be a networking issue as much as it seems to be a windows 7 holding on to incorrect credentials somewhere on the machine. When I try to map a drive from this particular laptop, it just asks for credentials for the share over and over again as if it's an incorrect password. However, doing it from my laptop, no issues with the same user account.
The user is able to ping the server he is trying to connect to and also do a successful tracert to it. There doesn't seem to be any loss of communication.
Any ideas?
Adam Leinss
Open a command prompt, then type net use. Do you see the drive mapped already in this list?
ASKER
No, it's not there. Not showing in windows or through command prompt.
Does it work under a different profile? What if you try different credentials logged in as him?
ASKER
No, I logged in as my own profile and mapped the drive as him and it did not work. Got an unidentified networking error.
ASKER
This is the error. Nothing shows up in the event viewer.
networking-error.jpg
networking-error.jpg
ASKER
Logged in as the user on a different machine, it works.
Can you connect to any UNC shares from this PC? Though it's very rare, I've seen two issues with not being able to connect to UNC shares:
Workstation service not started
Client for Microsoft Networks (under the properties of the local LAN connection ) becomes unchecked.
I would compare the NIC properties and the running services between a computer that works and one that doesn't. Failing that, updating the NIC drivers or reinstalling them would be my next step.
Workstation service not started
Client for Microsoft Networks (under the properties of the local LAN connection ) becomes unchecked.
I would compare the NIC properties and the running services between a computer that works and one that doesn't. Failing that, updating the NIC drivers or reinstalling them would be my next step.
ASKER
Yes, I can connect to just about every UNC share and mapped network drives except this one.
I will try reinstalling the NIC drivers and report back.
Thanks
I will try reinstalling the NIC drivers and report back.
Thanks
Also, try connecting to it using the FQDN, i.e. computername.domain instead of just computername. That is a suggestion I found when searching.
ASKER
I think this may have something to do with the intel network management software that's installed on the laptop. The laptop is trying to connect with an IBM AS/400 machine, not a windows network share.
I'm not sure if the intel software could be causing this to happen and the AS400 is rejecting the connection.
I'm not sure if the intel software could be causing this to happen and the AS400 is rejecting the connection.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the link Aleinss. I'll try it and report back when the user is available.
ASKER
Well, I was really convinced that this had to be the fix but it still did not work :( Same error.
ugh..
ugh..
How are you entering the username? If it's like domainname\username, try username@domainname.
ASKER
I'll try authenticating like that, but other win 7 PCs I am able to connect to the Iseries drive with his credentials the regular way.
domain\username
password
For the username field, do username@domainname
password field = same password?
domain\username
password
For the username field, do username@domainname
password field = same password?
Yes, it will pass the credentials a different way using that convention.
ASKER
Didn't work. Just took it as an invalid password.
I'm totally out of bullets on this one...maybe someone else can chime in?
ASKER
Wondering if anyone might be able to lend a hand on this.. I'm still having issues connecting to a networked IBM Iseries drive from a windows 7 laptop. I changed the LAN Manager security to allow LM and NTLM authentication and still not working. I am able to ping the server by name and IP.
ASKER
Was helpful getting me to the right place, but the fix turned out to be something else.
What was the ultimate fix?