Re: Problem connecting with wifi using WM5

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

My guess is that somewhere either in your PC or the router you are blocking
NetBIOS name resolution port 137 I believe. Again a guess on my part as I
don't really use Total Commander, but I suspect that it has it's own host
file and is using that for name resolution. I would suggest taking a look at
your firewalls.

You might also want to take a look at Pocket Host, if you install this
program you might not need to fix the problem with name resolution.
http://www.zimac.de/cestuff.htm

--
David Hettel

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

DISCLAIMER: This posting is provided "AS IS" with no warranties, and
confers no rights


"roydw" <royd@xxxxxxxxxxx> wrote in message
news:1160425924.215489.109950@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi David

I installed Resco File Explorer and tried the "autodetect mode". It
did not find either \\CHARLIE nor the IP for my wifi dongle on my PC
(but it did correctly identify the IP for my IPAQ wifi). Perhaps the
following summary will help:

On my PC:

When I ping CHARLIE, the results are OK and return the IP address for
my PC (assigned to the wifi dongle).

When I ping the IP address for my PC wifi dongle, the results are OK.

When I ping the IP address for my IPAQ the results are OK.

On my IPAQ hx2495:

Winfifofum finds my PC access point wifi broadcast and correctly states
its SSID and MAC.

When I ping the IP address for my PC (determined by running IPCONFIG
/all on my PC at a command prompt) the results are OK.

When I ping the computer name of my PC (using \\CHARLIE), I receive the
message "Cannot find host \\Charlie.

Total Commander works just fine (including full folder/file access of
my shared drives on the PC) using \\CHARLIE for the path name.

Neither WM5 File Explorer nor Resco Explorer are able to establish a
wifi link with my PC.

Any clues in all of this?

Roy



David Hettel wrote:
Well this tells me that the problem is in the conversion of \\CHARLIE to
the
ip address. File Explorer in the Pocket PC world will not accept a real
IP
address, like \\10.0.0.4 so that's not an option. If vxUtil can not ping
\\CHARLIE then you will not be able to access \\CHARLIE with Pocket File
Explorer, it's that simple. With vxUtil being able to ping your computer
by
IP address that tells me that your computer is not simply blocking all
ping
request. Is it possible that you have port 137 blocked in your firewall
or
router somewhere?

You might try downloading the free trial version of Resco File Explorer,
there is an option in it to scan your IP address and list all computers
on
that network. I would be interested in if it sees \\CHARLIE
--
David Hettel

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

DISCLAIMER: This posting is provided "AS IS" with no warranties, and
confers no rights




.

Relevant Pages

  • Re: Problem connecting with wifi using WM5
    ... I installed Resco File Explorer and tried the "autodetect mode". ... (but it did correctly identify the IP for my IPAQ wifi). ... When I ping the IP address for my PC wifi dongle, ...
    (microsoft.public.pocketpc.wireless)
  • Re: Problem connecting with wifi using WM5
    ... I have not had my firewall on for the wifi network (just while ... Now for the good news. ... I installed Resco File Explorer and tried the "autodetect mode". ... When I ping the IP address for my PC wifi dongle, ...
    (microsoft.public.pocketpc.wireless)
  • Re: Problem connecting with wifi using WM5
    ... With vxUtil being able to ping your computer by ... You might try downloading the free trial version of Resco File Explorer, ... that network. ... Please post any reply as a follow-up message in the news group ...
    (microsoft.public.pocketpc.wireless)
  • Re: ip-address of download.microsoft.com
    ... to an address when ping can't. ... there is a different wait for address resolution between the commands. ... there might be a server there doing something different now ... You may actually be able to see the first response by typing GET / ...
    (microsoft.public.windowsupdate)
  • Re: Hot! Server 2003 multiple IP binding order?
    ... Second, your said ping, but did not say pinging with what ... Did you cause a DNS or a WINS resolution ?? ... Microsoft MVP (Windows Server System: ...
    (microsoft.public.windows.server.dns)