Windows 7 Machines Cannot Connect to Windows 2003 Shares

As of a couple of months ago none of my Windows 7 Machines can browse network shares on our 2003 servers.

I have network connectivity (internet is fine, I can ping the servers both by Name and IP, NSLookup is fine, etc.) AND I can browse the Win7 shares from 2003 and even XP....?  Strange.  Similarly, The XP machines have no problem with the 2003 shares

Having done the Win7 research in advance I made sure to set the appropriate NTLM Local Policys on the Win7 PCs and that worked like a charm.  Naturally, when the shares became ghosts, I checked that they were still set correctly in case an update reverted to the default and I had been caught off guard.  Yup, all good.

I can't believe this is so difficult to figure out.

My set up is:

Win2003 DCs and servers
Win2008 Core File server (not yet configured)
Win7 PCs
WinXP Pcs

AV is Symantec Endpoint Protection v11.0.5 and current (which I will uninstall once I get an install package created and copied over to a Win7 PCs for reinstall)

Who is Participating?
LateNiteRConnect With a Mentor Author Commented:
I FOUND THE SOLUTION (Sorry Everyone!)

Searching and searching for an OS-Config or Patch issue lead me to ZERO but I began looking at other changes I'd made......and STILL came up short.  I'd given up.

I then began installing updates on my Son's PC (Win7 Pro) the other end of the house (see where this is going...?)  I happened to open windows explorer for some reason or  other when I noticed that HIS drive mappings to the NAS were still connected.  Naturally, I forgot about updating the OS (Something I'll be doing until NEXT Christmas) and looked at his settings.  All were identical to the other PCs.

THAT'S when it hit me.  I'd had bought a new Linksys/Cisco E1000 Wireless Router for one end of the house because it had GB LAN.  THAT was a change I hadn't anticipated to be a problem as WHO, in this day-and-age, would release a device that actually blocks Samba and other CIFS-like shares?!?!

To verify this, I took each PC into the other WiFi zone and each saw the NAS and the Win2003 shares perfectly.

I will award Nima the points as the largest contributor.
Make sure time is accurate across the file server, clients and the DCs.
NikSystems SpecialistCommented:
Can you please tell what error you receive when you try to browse the shares?
We're working on the same configuration Windows 7/Windows Server 2003 native domain and never had any issues.
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

LateNiteRAuthor Commented:
"Windows cannot access \\ServerName
Check the spelling of the name. Otherwise, there might...."

Error Code: 0x80070035
The network path was not found

I have also confirmed that Time is synch'ed
NikSystems SpecialistCommented:
Have you followed these steps to check the possible issues:

Turn off any firewalls for debugging. If the firewall is the problem, you'll have to configure it to allow access to "trusted zone" addresses. Note that some firewalls must be completely uninstalled to stop them from affecting your networking.

PING each computer by IP address, and if successful, PING by name. You can obtain the IP address of a computer by opening a command prompt (DOS window) and typing IPCONFIG. This should work for any Windows version. A failure here needs to be corrected before you go any farther.

Check your Services are Started on all PCs: Workstation, DHCP Client, DNS Client, Server, TCP/IP Netbios helper, Computer Browser.

All computers should be in the same workgroup for computer browsing to function properly. File & Print Sharing has to be enabled on any computer you wish to share files or printers from. You also need to actually share the resource in question from My Computer, right click on the drive/printer/folder, and select sharing.

If you encounter difficulties accessing computers that are visible in Network Neighborhood, make sure the computer being accessed has an account with the same name/password as the system connecting to it uses to login.

While the default NetBIOS setting is correct for normal network configurations, it's possible for it to be altered, and it costs nothing to make sure it's correct. NETBIOS over TCP/IP must be enabled for normal network browsing.
NikSystems SpecialistCommented:
Also, I think that Symantec Endpoint protection could be the culprit. Can you try to remove it only temporarily?
LateNiteRAuthor Commented:
Windows Firewall IS disabled and as I said originally "...I can ping the servers both by Name and IP, NSLookup is fine, etc."

The NIC was set to the default and was getting its NetBIOS settings from DHCP.  I changed that to "enabled" which didn't change anything.

My network is a MS Domain and file sharing is enabled hence being able to browse shares between XP and 2003.  I can even browse Win7 shares from XP and 2003.


I will uninstall SEP to see if that is the culprit as soon as I can push-down a package to reinstall.
LateNiteRAuthor Commented:
I uninstalled SEP and nothing's changed.

I'm going to reinstall it and then uninstall all Windows updates since the July 2010.  It's after that things seemed to break down.
LateNiteRAuthor Commented:
....and yes, the E1000 does have the latest firmware installed and research indicates that Cisco does not yet have a solution to this behavior.
LateNiteRAuthor Commented:
Nima.  To keep this solution easy to find I have created a 2nd post to award your points.
NikSystems SpecialistCommented:
Glad that you've solved it.
Thanks for the points and I wish you Happy Holidays!
LateNiteRAuthor Commented:
The Linksys E1000 Blocks Samba and other shares.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.