I cannot get a drive or UNC path to map between two Windows 2008r2 servers but they map anywhere else in the network and all other servers can map to them.

I have 2 windows 2008r2 servers on a windows 2012r2 domain. For an application to run on ServerA a path must be mapped to ServerB such as \\ServerB\Folder\Folder2
The App stopped working today and I can no longer map the path even manually by using UNC path. I tried to manually map a drive letter just as a test but I cannot map anything from ServerA to ServerB. They can PING each other. ServerA can map to any other server in our network. ServerB can map to ServerA. I tried mapping from ServerA to ServerB by IP address but the connection still gets rejected. If I do a NET USE on ServerA I do not see a connection. I have tried rebooting ServerA several times without success. I cannot reboot ServerB at this time. I am running out of ideas. I tried a NETSTAT on ServerB and do not see any incoming connection from ServerA. i am running out of ideas....oh yes I did a FlushDNS on both....any other suggestions? This has worked for years and it only seems to be from ServerA to ServerB....I talked to our network team and no ports were blocked or firewall changes today
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I believe you will find the issue in your Windows Firewall Configuration..

Please check your "File and Print Sharing" settings and compare the two servers.

Specifically, check the "Echo Request" sections

Please enable this for both inbound and outbound requests. IPV4 and IPV6

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Try checking the IP settings. Make sure that IPv4 is preferred over IPv6. However, do not unbind IPv6 from the NIC.
DonNetwork AdministratorCommented:
On server B have you tried taskmgr and restarting explorer.exe ??
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

David Johnson, CD, MVPOwnerCommented:
if you do a
net use *  \\ServerB\Folder\Folder2
net use z:  \\ServerB\Folder\Folder2 (assuming drive Z: is free)
do you get a 53 error?

You did not say whether or not these machines are in a workgroup or a domain. Guessing workgroup
Thor2923Author Commented:
on the net use attempt, I got error 67  network not found....I tried telneting using port 445 and it would not connect. I notified our network team. The port might be blocked
Shaun VermaakTechnical Specialist IVCommented:
I notified our network team. The port might be blocked
Check Windows Firewall as per the first comment. This is the OS, not networks. Check file and print rule, not echo request. Echo request is working otherwise you would not be able to ping
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.