|25 Apr 2013||#1|
| || |
Network shares accessible via IP but not share names
A customer is having a problem on one workstation where "shares" on the server can accessed through the Homegroup and also via mapped drives if mapped using the server IP, however they cannot be accessed using the share name. For instance if share "\\server\data" is created I can map it to Z: using 192.168.0.100 (server IP) using the string
and connect without problems, however if I try to map Z: to:
it will fail, specifically saying the user account credentials are wrong. If we go into Explorer the network shares are displayed but cannot be accessed. However the shares can be accessed through the Homegroup!
There is another workstation in the office, also running Windows 7 HE, with the same mapped drives accessing the same shares without problems. We've looked at the network settings and as far as we can tell they are same. The Windows Firewall is turned OFF on the workstations and the server.
The PC the customer is using for a server is also running Windows 7 HE and we wonder if that might be the problem? We're going to get him to change to a proper server OS eventually, but we're trying to make his current setup work for the short term. Any suggestions will be appreciated
|My System Specs|
|Similar help and support threads for2: Network shares accessible via IP but not share names|
|samba share is not accessible from Windows 7 client...||Network & Sharing|
|How would one share or connect to a network share from WinRE||Network & Sharing|
|Network not accessible, network address invalid||Network & Sharing|
|BSOD when accessing network or network shares via Wireless||BSOD Help and Support|
|Old File Names Reappearing on Network Share||Network & Sharing|
|Network drives are accessible but still have red X||Network & Sharing|
|"Share with -> Specific people..." shares all libraries||Network & Sharing|
|Our Sites ||Site Links ||About Us ||Find Us |
© Designer Media Ltd
All times are GMT -5. The time now is 11:55 PM.