Device won't connect

  • Thread starter Thread starter Geoff Callaghan
  • Start date Start date
G

Geoff Callaghan

I'm having trouble connecting to my device through Visual Studio .NET. I
never used to have this problem, but I recently got a new OS from my vendor,
and now it doesn't work. I have it set to go through Active sync, and to get
an IP address automatically through Active Sync. Is there something else I
can check?

The basic symptom is that it says "establishing connection", and that
message stays there until I kill the program through Task Manager.
 
Are you using the smart device authentication utility (sdauthutildevice.exe
on the device)? I can never coonect to a non PPC device without.

--
Chris Tacke
Co-founder
OpenNETCF.org
Has OpenNETCF helped you? Consider donating to support us!
http://www.opennetcf.org/donate
 
Does that have to be compiled into the operating system? Or is it something
I can just copy over there?
 
OK, I tried that, and it still isn't working. Just for clarity: I ran the
utility on my device, and it reported two available IP addresses, neither of
which I recognize. I pressed start, then opened my Visual Studio project,
and hit Establish Connection. I see the same symptom...VS says it is
establishing connection, nothing happens.
 
You have to use the Smart Device Authentication utility on the desktop
before you just haul off and try to connect. If you've installed the
Windows CE utilities for VS.NET 2003, it should be in the tools menu. You
run it, enter the IP of the device and tell it to connect. When it's
established a connection, close it. The window on the device (showing the
IP addresses), will close in response. Then, you can adjust your Options
for device connection to use TCP/IP and to use the IP address which you
entered to the SDA.

Paul T.
 
I have the same problem. Trying to connect a HP3715
to a smart device project in VS.NET 2003.
The device is connected fine through ActiveSynch.
However, VS gives the message:
"Make sure the device is physically connected to the development computer"
This has never been a problem before.
Could it be SP2, a firewall or something?
 
What about the SDK? I got a new SDK With the new OS, and installed it. Do I
have to do something more with it, like somehow tell Visual Studio where it
is?
 
You should install the SDK, but that's separate from establishing
communications with the device. What happened when you did the things that
I mentioned in the previous message?

Paul T.
 
I connected with the USB cable. I ran the utility on the device, and it
listed two IP addresses. I pressed start. I ran the utility on the desktop
and typed in one, then the other, IP address. Both time it said the
connection had failed. Did I miss a step? Am I supposed to use a specific IP
address, or just the one it tells me?
 
OK, for that Smart Device Authentication Utility, you really need a real
network connection. Just plugging the USB cable from one end to the other
doesn't qualify, although it might tell us something if you gave us the IP
addresses it shows.

I'd use the ActiveSync transport and startup server, in the USB case, as
you've done unsuccessfully. If you have a real network connection, use that
and the SDAU and it should work. Otherwise, you need to talk to your device
vendor and get them to figure out what's going on. It appears that their
device is broken.

Paul T.

Geoff Callaghan said:
I connected with the USB cable. I ran the utility on the device, and it
listed two IP addresses. I pressed start. I ran the utility on the
desktop
and typed in one, then the other, IP address. Both time it said the
connection had failed. Did I miss a step? Am I supposed to use a specific
IP
address, or just the one it tells me?


Paul G. Tobey said:
You should install the SDK, but that's separate from establishing
communications with the device. What happened when you did the things that
I mentioned in the previous message?

Paul T.

Geoff Callaghan said:
What about the SDK? I got a new SDK With the new OS, and installed it. Do
I
have to do something more with it, like somehow tell Visual Studio
where
it
is?


"Paul G. Tobey [eMVP]" <ptobey no spam AT no instrument no spam DOT
com>
wrote in message You have to use the Smart Device Authentication utility on the desktop
before you just haul off and try to connect. If you've installed the
Windows CE utilities for VS.NET 2003, it should be in the tools menu.
You
run it, enter the IP of the device and tell it to connect. When it's
established a connection, close it. The window on the device (showing
the
IP addresses), will close in response. Then, you can adjust your Options
for device connection to use TCP/IP and to use the IP address which
you
entered to the SDA.

Paul T.

OK, I tried that, and it still isn't working. Just for clarity: I
ran
the
utility on my device, and it reported two available IP addresses,
neither
of
which I recognize. I pressed start, then opened my Visual Studio
project,
and hit Establish Connection. I see the same symptom...VS says it is
establishing connection, nothing happens.

You can copy it over. It's distributed with Studio.

--
Chris Tacke
Co-founder
OpenNETCF.org
Has OpenNETCF helped you? Consider donating to support us!
http://www.opennetcf.org/donate


Does that have to be compiled into the operating system? Or is it
something
I can just copy over there?
Are you using the smart device authentication utility
(sdauthutildevice.exe
on the device)? I can never coonect to a non PPC device
without.

--
Chris Tacke
Co-founder
OpenNETCF.org
Has OpenNETCF helped you? Consider donating to support us!
http://www.opennetcf.org/donate


I'm having trouble connecting to my device through Visual Studio
.NET.
I
never used to have this problem, but I recently got a new OS from
my
vendor,
and now it doesn't work. I have it set to go through Active sync,
and
to
get
an IP address automatically through Active Sync. Is there
something
else
I
can check?

The basic symptom is that it says "establishing connection", and
that
message stays there until I kill the program through Task
Manager.
Click to expand...
Click to expand...
Click to expand...
 
Back
Top