http://www.dotnet247.com/247reference/a.aspx?u=http://www.opennetcf.org/Forums/t
opic.asp?TOPIC_ID=305

has a pretty good overview of my problem. I think it all started with the
latest XP Service Pack 2 RC2 (2162) that did something with subnetted
devices such as my Axim X5. When docked, and having run the
SDAuthUtilDevice.EXE utility, I am told the device IP is 192.168.55.101 and
I key this IP into the SDAuth.exe utility on the VS.Net 2003. However... I
get the following error:

"Device IP address not found. Run the device component of this utility to
find the IP address of the device. System.Net.Sockets.SocketException: No
connection could be made because the target machine actively refused it at
System.Net.Sockets.Socket.Connect(EndPoint remoteEP) at
Microsoft.SDAuthUtil.Form1.DoConnect()"

Now at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vstechart/ht
ml/grfUsingEmulatorInSmartDeviceProjects.asp
there is the hint that reinstallation of the CF pieces of VS.Net2003 would
help, but, as you gentle readers might be guessing by now, it did not. Also
mentioned in the various google searches turned up by a word search was the
possibility the the "ProxyKeys" subkeys of the registry might be corrupted;
of course, they are not.

Not much left at this point except to post this to the VS.Net groups and/or
XPSp2 (on the offchance this is where my problems started). It (SP2) clearly
doesn't much like or trust the fleshware on the other side of the keyboard
from it.

TIA,
Alex