Can't access share by name, but can via IP or FQDN
Posted on 2012-04-11
We have had a recent issue at work where computers newly imaged with SCCM work fine in our building but then sometimes (not always) when they get sent to other offices on the corporate network - the users can login and everything works fine - except connecting to network shares.
When we image the computers another way (with BartPE) then everything works fine.
Our imaging guy has been creating a new image to try to fix the problem, but it's driving me crazy that I don't know what the problem IS! We still have several users scattered around that have freshly imaged computers that are having this issue. As a workaround, I have mapped their drives using the ip address instead.
Here is some of what I have done in troubleshooting:
" net view //servername" gives this results
System error 53 has occurred. The network path was not found.
"net view //ipaddress works fine
File and print sharing is turned on.
Windows Live Sign-in Assistant is NOT installed.
I can ping the server by name and it works fine.
I can browse to and map drives using the FQDN just fine.
I have flushed the dns, reset the winsock settings, and checked to make sure that the advanced TCP/IP settings match those of computers that are working correctly.
The problem happens on Windows XP and Windows 7 computers.
One common thing with all of them is that they all have a Cisco 7940 IP phone, but they are not all plugged in through the phone - so I'm not sure how that could be a problem. Also, one of the users was recently reimaged using BartPE and she is plugged in through her Cisco 7940 phone and working fine now. She had been reimaged TWICE with our existing SCCM image and had the issue. I have made screenshots of all of her network settings so that I can try to duplicate them for others having the issue, but I'm not having much luck.
Any help would be appreciated. I've been working on this problem off and on for three weeks. Thanks so much!