Windows – Accessing network share in explorer on different domain not prompting for credentials. Access is denied

The following advice does not help you to 'purge or empty Windows Explorer’s network username and sharename cache' (as you asked). But it will allow you to connect to (essentially) the same share or the same server using a different username.

The trick is to use the IP address of the remote server.

(Also,

if it's Samba on the remote side,

• you could setup smb.conf to contain netbios aliases = firstname, secondname, thirdname and you'll have even more options

if it's a Windows AD member server on the remote side,

• you could create a different 'Domain Name Alias' for your server,

and you'll have even more options. In all these situations, the connecting client will behave as if it connected to a different server.)

When troubleshooting similar issues, I have found that the best solution is to triage using Wireshark to make packet traces. You need to figure out what is actually going on when the machines communicate. Mirror a port on your switch and run Wireshark three times -- twice on this machine with different users and then once on the same mirrored port using another machine that does work. Look for periods where traffic between the server and client stops for long periods, and figure out which client is waiting and which is not responding. Compare the three traces and see the differences in all communication. Somewhere in there you will find a clue that will show which continent the problem is actually on, if not the street address. Good luck!