Windows 7 can't access Server 2003 shares
I've done a lot of research on this problem and as of yet have not come up with any solutions that work. In the past we had a Server 2003 32-bit server hosting the domain (we'll call it SRV1) with all Windows XP workstations. Well, we outgrew that server and needed to purchase another one. Bought one running Windows Server 2003 64-bit (we'll call it SRV2) to replace SRV1, which was moved to a satellite location but is still on the domain. Recently we purchased a few Windows 7 boxes to test on the network before we begin migrating newer computers to it. Now SRV1 is connected to SRV2 via a VPN connection. Anyway, the problem is that the Windows 7 boxes cannot access the network shares or RDP to them and running a port scan shows the ports as being closed. The kicker is that we can VPN from the boxes to the network (while inside the building) and get onto the shares and RDP. There is no firewall running anywhere within the network, service isn't even started, so this isn't the problem. I also have a personal laptop running Windows 7 (used to run Vista, worked fine) that is not on the domain and this also does not work. I've tried the Network Security: NT LAN Manager authentication level change, making sure clocks are the same (within a minute at least), and whatever other advice I could find but absolutely nothing has worked. Has anyone experienced this same issue and found a resolution for it? I'd even settle for suggestions relating to something close as this is completely blocking us from deploying Windows 7 at all.
October 14th, 2010 1:18pm

Have you enabled Network Discovery in each Windows 7 system? How does it work if you try to access other computers via IP address? You may run IPconfig/all in cmd command and check the status of the connections. Please verify that if the DNS server configuration is properly. In most cases the DNS server should be the DNS server of your domain. Additionally, please let us know if all Windows 7 computers connect to the domain with a router or layer 3 switch. If so, I suggest you switch a common layer 2 switch and check the result.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
October 19th, 2010 3:18am

We discovered what the problem was. We had an 8 port switch that we removed from the server rack when we replaced it with a 24 port switch. Well another tech used this old switch to hook up a couple extra computers, not realizing that it had the same IP as our new server. We discovered this by getting lucky and today when I looked at the IP through a browser it resolved to the switch and not the server. We hunted this switch down, changed it to DHCP, and magic everything worked again. What is odd about this is that the XP machines apparently didn't have much of a problem with this (even the ones connected to the switch) but the Win7 machines absolutely would not work with it. Thanks for the reply, and maybe this will help someone else in the future!
October 19th, 2010 4:09pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics