Link to home
Start Free TrialLog in
Avatar of swgit
swgitFlag for United States of America

asked on

Windows 2008 R2 File Share

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.
Avatar of Edward Pamias
Edward Pamias
Flag of United States of America image

did you check the share on B, to make sure its setup correctly? Permissions, the name etc...
Avatar of swgit

ASKER

yes.. i did.. all other subnets get to it just fine
ASKER CERTIFIED SOLUTION
Avatar of Wayne88
Wayne88
Flag of Canada 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
Avatar of swgit

ASKER

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)
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.
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
Avatar of swgit

ASKER

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.
Thanks for the points and getting back to us.  Cheers!