Archived from groups: microsoft.public.pocketpc (
More info?)
None of that works from the cradle because of what I mentioned earlier. The
IP suite is very limited. You should have better luck with BT setting up a
PAN connection, but it is dependent on the PAN implementation, PC and PPC.
IR to the PC is just another ActiveSync connection, and a BT ActiveSync
connection is....just another ActiveSync connection. To ensure you get all
the IP type stuff you want you will need to connect into the network via
WiFi, a cabled ethernet (which is possible with some PPCs that have CF or
PCcard slots), or a BT AP. You can make it work doing an AdHoc connection
via WiFi to a desktop that has an internet connection, but that is not
trivial. It just involves setting up ICS on the desktop, but getting the
adhoc connection and the ICS right can be dodgy.
Wifi to an access point you can most certainly ping your desktop. You won't
be able to ping your PPC however. I don't believe it responds to that SNMP
request, just as it has no real capability to share files or folders. You
won't see your PPC from your PC in network neighborhood, and you can't get
to it's files that way. If you think about it, the only way you get to
attach to your PC is you right click a folder on the PC and share it. Right
click, or tap and hold, a folder on the PPC. You don't see a share option,
do you?
Printing from the PPC isn't a native thing anyway. You need some third party
solution. Whichever you pick, it should provide information on how to
actually use it. Normally the BT option requires a BT capable printer, just
as the IR option requires an IR equipped printer. IP options require the
PPC itself to be on the network, i.e. it has an IP address on the network,
like 192.168.1.200, not that ActiveSync squirrelly subnet IP. The HP one
works fine for me and it's free. It is a bit limited in printer selection
compared to some of the commercial ones, but I have the printers it
supports.
--
Sven, MS-MVP Mobile Devices
"GPF" <GPF@discussions.microsoft.com> wrote in message
news:5CEE0872-B73F-4D8E-915B-A6045953A254@microsoft.com...
> Not at all. I've a printer, I share it but I can't use it.
>
> I'd like to print directrly from 1940. If tcp/ip or sharing are not
> working... bluetooth or irda?
>
> And what if I want to use some "lan discover"? Tha same result?
>
> Thanks by now!
>
> "Neil Smith [MVP Digital Media]" wrote:
>
> > Have you got a firewall switched on, on the PC, which might reject
> > Ping packets ?
> >
> > On Fri, 20 Aug 2004 00:27:03 -0700, GPF
> > <GPF@discussions.microsoft.com> wrote:
> >
> > >OK... this will help me.
> > >
> > >But now: why I can't ping my PC? I share a printer on PC but I can't
use it.
> > >I suppose my 1940 configuration is somewhat correct (I can use PIE from
> > >1940...) as you say my PC act as a router.
> > >
> > >Thanks!
> > >
> > >"Sven, MVP-Mobile Devices" wrote:
> > >
> > >> The ActiveSync connection only supports a subset of the IP protocol.
As such
> > >> not everything is supported. To do network browsing in a Windows
network you
> > >> actually have to support UDP as well, which this connection does not.
The IP
> > >> you are getting is because the AS process sets up a small network
between
> > >> your PC and PPC. You will find your PC is 192.168.55.100 in that
network. It
> > >> also sets up the PC as a router to allow the Internet Pass Through we
are
> > >> all familiar with.
> > >>
> > >> You will only get the full IP capability if you connect your PPC to
the
> > >> network directly. Normally that would be via an ethernet CF card,
WiFi to an
> > >> AP, or something like that. Not sure what options you have with a
1940.
> > >>
> > >> --
> > >> Sven, MS-MVP Mobile Devices
> > >> "GPF" <GPF@discussions.microsoft.com> wrote in message
> > >> news:A6ADF346-6ADB-46E2-AFCA-A65EB2EB8E59@microsoft.com...
> > >> > Hi,
> > >> >
> > >> > I've an iPAQ1940 connected via usb to my PC. Why I can't see any
> > >> > device/share on my LAN? How can I set my iPAQ to get an IP address?
> > >> > vxIPConfig get a 192.168.55.101. I've a DHCP server in my LAN...
> > >>
> > >>
> > >>
> >
> >
/tinyurl.com/33eyz
Facebook
Twitter