Windows 2008 R2 File Share

swgit
swgit used Ask the Experts™
on
Dear Experts,

I have two Windows server on different subnets and domains - let's call them A.local and B.local.  I can ping both of them by IP, hostname and FQDN.  

When I "\\hostnameB\share" on A, I got "Windows cannot access \\hostname\share.  Check the spelling of the name.  Otherwise, there might be a problem with your network.  To try to identify and resolve network properties, click Diagnose.  Error code: 0x800004005 Unspecified error."

Everything works find if I do "\\hostnameA\share" from B.

I checked the firewall, virusscan and such... nothing work on A when trying to get to resources on B.  Could you please give me some clues?  Thanks.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Edward PamiasTeam Lead RRS Desk
Top Expert 2016

Commented:
did you check the share on B, to make sure its setup correctly? Permissions, the name etc...
swgitIT Professional

Author

Commented:
yes.. i did.. all other subnets get to it just fine
Top Expert 2015
Commented:
STEP1

It almost sounds like Windows firewall is stricter on hostnameA than hostnameB.  Are both servers running Windows 2008?  If so, compare the firewall rules on both are similar and you explicitly allow SMB, filesharing services and port through the firewall on hostnameA.

- In Windows Firewall, click Advanced settings, and in the console tree, click Inbound Rules.
- Under Inbound Rules, locate the rules File and Printer Sharing (NB-Session-In) and File and Printer Sharing (SMB-In).
- For each rule, right-click the rule, and then click Enable Rule.

STEP2

Also, if you are accessing a share on hostnameA then try logging in using a username/account from domain of hostnameA.  Remember that to state the username as "domain\username"  If that doesn't work, then try a test share folder with EVERYONE permission, and try to login using a local account "hostname\username".  If any of those works then you know it's a Windows Authentication issue.  If you don't get that far then it may be a firewall issue.  Also check the event logs for hints on the server hosting the share for clues.
JavaScript Best Practices

Save hours in development time and avoid common mistakes by learning the best practices to use for JavaScript.

swgitIT Professional

Author

Commented:
The only difference I found was that Windows Firewall on B was completely OFF... so I went ahead and turned OFF Windows Firewall on A... also disabled GP related to the Firewall, and force gpupdate.  However, the same error occurs.  I tried to connect to the share, I got Error code: 0x80070035 - the network path was not found (this error is for both hostname and IP)
Top Expert 2015

Commented:
But you are able to ping this same server using hostname as well as IP right and that you have no problem mapping to the same server from a machine within the same domain.  Is this correct?

Can you check something quickly, ensure the TCP/IP NetBIOS Helper service is running on both the workstation as well as the server you're trying to connect to?  Then try again.
Edward PamiasTeam Lead RRS Desk
Top Expert 2016
Commented:
This is what Microsoft asked another person to do to fix their issues. I would assume you would do this on the server with the issue. If what Wayne88 does not fix it, try below.

1. Remove the DNS entries from TCP/IP properties

2. Restart the machine

3. Notice, sharing is now working!

4. Reconfigure the DNS entries in TCP/IP properties
swgitIT Professional

Author

Commented:
Thanks, both.  I ended up talking to MS, and with the use of Microsoft Network Monitor 3.4, we were able to pin down the problem caused by an acknowledgement reset on port 445 at the perimeter fw.
Top Expert 2015

Commented:
Thanks for the points and getting back to us.  Cheers!

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial