Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Cannot access Windows 2012 Server File Shares from Windows 2003 Server

Posted on 2013-12-16
14
Medium Priority
?
2,009 Views
Last Modified: 2016-04-26
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
Comment
Question by:humphrey06
  • 7
  • 6
14 Comments
 
LVL 13

Expert Comment

by:Norm Dickinson
ID: 39722286
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
 

Author Comment

by:humphrey06
ID: 39722315
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
 
LVL 13

Expert Comment

by:Norm Dickinson
ID: 39722390
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
Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

 

Author Comment

by:humphrey06
ID: 39722439
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
 
LVL 13

Expert Comment

by:Norm Dickinson
ID: 39722448
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
 

Author Comment

by:humphrey06
ID: 39722454
I am logged in as a domain admin on the Win2003 server and cannot see the  Win2012 share.
0
 
LVL 13

Expert Comment

by:Norm Dickinson
ID: 39722458
Is there anything that comes up in the event log when you attempt to connect?
0
 

Author Comment

by:humphrey06
ID: 39722717
No event log entries.
0
 
LVL 13

Expert Comment

by:Norm Dickinson
ID: 39722732
Patches and updates are current on affected machines? Are your DNS settings the same for all affected machines? (servers and clients)
0
 

Author Comment

by:humphrey06
ID: 39722785
Yes all updates.

Yes, same DNS settings.
0
 
LVL 13

Accepted Solution

by:
Norm Dickinson earned 2000 total points
ID: 39722794
Have you restarted the servers?
0
 

Author Comment

by:humphrey06
ID: 39731874
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
 
LVL 13

Expert Comment

by:Norm Dickinson
ID: 39731887
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
 

Expert Comment

by:logictrail
ID: 41566780
I had to add the windows feature smb v1 in our Windows 2012 r2 server to get it work. Somehow it was removed.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
A procedure for exporting installed hotfix details of remote computers using powershell
Windows 8 comes with a dramatically different user interface known as Metro. Notably missing from the new interface is a Start button and Start Menu. Many users do not like it, much preferring the interface of earlier versions — Windows 7, Windows X…
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…

783 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question