Remote command-line access to a Windows machine

Install Powershell 2.0

In powershell on the server enter:

set-executionpolicy remotesigned -force

enable-psremoting -force

Then from a remote machine (that has powershell enabled) initiate a remote connection:

etsn -cred username -comp targetname

If you are on the same domain and have proper authorization you can skip the '-cred username' part, but I've found if you're crossing domains with non-mutual trust then it is necessary to use credentials of the remote domain.

Also if you want to just issue one command you can do something like...

icm targetname {$host }

The above should be enough to get you started down the magical world of powershell remoting.

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!