Link to home
Start Free TrialLog in
Avatar of Blake Weaver
Blake Weaver

asked on

Cannot access shared files from another server on internal network from my SBS 2011.

I am running SBS 2011 environment (192.168.0.203).  I have another Windows Server 2008R2 server(192.168.0.202) on the network and from my SBS i cannot access shared network folders from the 2008r2 server.  Windows Network diagnostic utility is no help.  However I can access the network shares from any other computer on the internal network just fine.  I have tried browsing by IP and by server name.  I can ping the 2008 server from my SBS.  Anyone shed some light on this very frustrating problem or help me diagnose it further?  And yes i am 100% sure the path in the below screenshot User generated imageis correct.
Avatar of VB ITS
VB ITS
Flag of Australia image

As a first step, have you tried disabling the anti-virus software on your servers?
Did you ever try to use shares of a different PC from SBS for test?
Check for Event Log entries re Security on both server and SBS - it might deny or require some "unsecure" authentication method.
Is the second server joined to the domain or totally independent on its own workgroup?

If it is separate and not on the domain then check the cached windows credentials and see if they are still valid.

Check the share permissions to make sure that the user account that you are trying to access it with has the correct permissions.
Avatar of Blake Weaver
Blake Weaver

ASKER

Yes the 2008 server is on the domain, and the creds are correct because i can access the shares using the creds from another computer on the network.    From my SBS its not even prompting me for username/password.  In conclusion, from my SBS i can ping and rdp to the 2008 server i just cant detect that anything is shared out.  But i can access the 2008 shares on other PCs.  And i have already ruled out Anti-virus as the cause
I have also learned that the problem seems to be residing on the SBS side, not my 2008 share.  I shared some files out of my personal laptop which is on the network(not on domain) and it wont connect to my laptop as well.
Can you try connecting via the IP address and see if it does the same
ip or hostname, neither work but hostname does resolve properly to the correct IP
SOLUTION
Avatar of Qlemo
Qlemo
Flag of Germany image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Under Security there are 0 results for Warnings, Errors, or Critical events
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Yes windows firewall is disabled.  But like i said i cant connect to any shares on the network from my SBS.  Some are on the domain, some aren't.

Heres the results:
C:\Users\blake>tracert 192.168.0.202
Tracing route to ed2.1stmc.local [192.168.0.202]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  ed2.1stmc.local [192.168.0.202]
Trace complete.
C:\Users\blake>
After doing some research on my own i think i found it(see screenshot).  Just not sure what option to choose
File-PrintSharing.PNG
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Yep, that would definitely explain your issues. FYI all of those boxes are ticked by default in SBS 2011, so go ahead and tick all of them then reboot the server if possible. Hopefully this will fix your issues going forward.
when i check the boxes it wants me to install something and i get stuck on this screen(see attachment). Ideas?
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
thanks for all the suggestions guys.  Yes i know this would of been an impossible task to troubleshoot unless you had hands on.
Actually it's more thank you for telling us what the issue was. At least the next time we see these sort of symptoms, we'll know where to check first :)