• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2128
  • Last Modified:

Cannot access Windows 2012 Server File Shares from Windows 2003 Server

I installed a new Windows 2012 File Server last week.  At the time of the initial install, both Windows 2003 Server and Copier/Scanners could access the Win2012 Shares via SMB.

Today, neither Windows 2003 computers nor copier/scanners (which scan to it via SMB file share) cannot access the file shares.

As far as I am aware, all Win7, Win8 and Win2008 Servers can access these shares.
0
humphrey06
Asked:
humphrey06
  • 7
  • 6
1 Solution
 
Norm DickinsonGuruCommented:
Make sure that either both servers are part of the same domain or that the users are set up with full permissions on each server. Also try to use the IP address to connect as well as the UNC address, as one may work more reliably than the other in some cases. For instance, use either \\servername\sharename  or \\192.168.1.100\sharename to connect, to see if either one works. Check your firewall settings and event logs to see if there is any indication of what is preventing it, and possibly a restart of the servers would be a reasonable step, if they are not too busy handling other users. No sense cutting anyone off without notice...
0
 
humphrey06Author Commented:
Thanks for your response.  Both Win2003 and Win2012 are domain controllers.

I have also tried to connect using the IP address (e.g. 192.168.1.100).

When trying to connect either using \\servername\sharename  or \\192.168.1.100\sharename I receive message:  "Windows cannot find 192.168.1.100.  Check the spelling and try again."

The odd thing is both 192.168.1.100 and servername ping successfully.
0
 
Norm DickinsonGuruCommented:
Are both servers on the same subnet mask, but with different IP addresses? For instance, one server is at 192.168.1.100 and the other at 192.168.1.101? (Or anything that starts with 192.168.1.xxx)
Does the same user name exist on both servers, with the same passwords? Are permissions for sharing set up?
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
humphrey06Author Commented:
They are both domain controllers on the same subnet.  This all worked last week.  For whatever reason, none of my Win2003 servers can connect to this Win2012 share while all of my Win7, Win8 and Win2008 computers can.
0
 
Norm DickinsonGuruCommented:
So your Windows 7, 8 and Server 2008 computers can al see both the 2003 server and the 2012 server?
It sounds like a permissions setting, group policy change or maybe a firewall issue. Or a password got changed. Try entering the credentials again on the copier?
0
 
humphrey06Author Commented:
I am logged in as a domain admin on the Win2003 server and cannot see the  Win2012 share.
0
 
Norm DickinsonGuruCommented:
Is there anything that comes up in the event log when you attempt to connect?
0
 
humphrey06Author Commented:
No event log entries.
0
 
Norm DickinsonGuruCommented:
Patches and updates are current on affected machines? Are your DNS settings the same for all affected machines? (servers and clients)
0
 
humphrey06Author Commented:
Yes all updates.

Yes, same DNS settings.
0
 
Norm DickinsonGuruCommented:
Have you restarted the servers?
0
 
humphrey06Author Commented:
I restarted all servers (including the Win2012R2 with problem) with no change to problem.  Waited a couple of days and tried rebooting on the the Win2012R2 server and suddenly all was working.

As a side note, I was thinking (and still do also) that it may be an issue with SMB vers 1 vs vers 2 &3.  However, while the problem was occurring, I used powershell to show SMB versions running on Win2012R2 server and SMB vers 1 (used by Win2003) was showing enabled.  I'm wondering if it was not working though showing "enabled".  This is the only thing I can find different with Win2003 vs. Win7/Win2008 fileshare access.

I have a feeling this may raise its head again but thanks for all who attempted to help!

Could someone help me determine the most appropriate way to close this out and whether or not we should say that restarting the servers "fixed" the problem and if so, should it be a Grade A or B?
0
 
Norm DickinsonGuruCommented:
The best approach is to determine the answer that got you through the symptom and award that answer the bulk of the points - but if others also contributed, split some of the points between them. It is also customary to award the answer as an A unless it was really not helpful, as points are free, and we are only allowed to keep our membership as experts if we collect enough points each month - so it really does make a difference.
0
 
logictrailCommented:
I had to add the windows feature smb v1 in our Windows 2012 r2 server to get it work. Somehow it was removed.
0
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.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

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

  • 7
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now