Avatar of swgit
swgit
Flag 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.
Windows Server 2008

Avatar of undefined
Last Comment
Wayne88

8/22/2022 - Mon
Edward Pamias

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

ASKER
yes.. i did.. all other subnets get to it just fine
ASKER CERTIFIED SOLUTION
Wayne88

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
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)
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
Wayne88

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
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
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.
Wayne88

Thanks for the points and getting back to us.  Cheers!
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.