Wi-Fi Problem

Howard2k · 07-15-03, 09:31 PM

Here's a strange one.

My other PC is toast right now so I'm using my "backup". I need to copy some files from my backup to my PPC so I'm trying via Explorer, but I get the:

Quote:

Connecting to Server

Quote:

The network path was not found

Quote:

Network resources cannot be found or you do not have permission to access the network. Contact your network administrator.

Hmm... So I did some playing around.. My settings are all correct.. I can surf the net OK.

It's starting to annoy me.. I've tried mapping via IP Address (\\192.168.1.4) and via hostname (using PocketHOSTS too).

Still the same.

So I did a packet trace and I'm seeing packet going out to from the PPC on port 137 to 192.168.1.255!! The broadcast address!! WTF?

So I tried another IP, 192.168.1.1. this is my router, clearly it's not sharing any files but that's not the point.

And the same!! Tries to connect to 192.168.1.255!

Anyone have any idea? I'm seeing no ARP requests, just connections to the broadcast address...

Howard2k · 07-15-03, 09:43 PM

Manually entered the IP information (rather than DHCP)... No change...

ikehiker · 07-15-03, 10:28 PM

You say you are trying to copy by Explorer - you mean as a network share? If that's correct, have you tried ActiveSync? Have you ever established a partnership between the Ax and this computer? I know it doesn't explain why your Ax isn't accessing it via the network but it would provide another option for getting the files over.

Howard2k · 07-15-03, 10:33 PM

I have not.. Not trying to copy via AS though, just from the Explorer on PPC...

If I HAD synced before then that would be a good option :)

chuckcoger · 07-16-03, 02:48 PM

Probably all ready made sure this was on, but I'll ask it anyways.

Is File and Print Sharing for Microsoft Networks on the PC?

If so are the appropriate directories shared?

I know these are basic configs, but the host side was never mentioned so I thought I would ask just to make sure. The reason you are seeing the traffic on port 137 (Netbios NS) to the broadcast address is to look for any shares on the net and apparently it see's none. Your PPC is browsing for "anything" since it can't connect to the host. There maybe several reasons, no shares, mapping to \\x.x.x.x without a share extension like \\x.x.x.x\Shared Folder, No access for Shared and Print Services on the PC, or the router could be blocking 137 to allow mapping of the drive which I would doubt on todays routers. I would rebuild any shares and also try looking in reverse if you can, or to another machine if you have one.

Howard2k · 07-16-03, 05:32 PM

Thanks Chuckcoger. I did check that. FROM MEMORY NB broadcasts are 255.255.255.255 not directed broadcasts on 192.168.1.255. Certainly shared and verified via NET SHARE. Thanks for the tips though. I'll do some research. Been a long time since I did Microsoft networking "in anger". I'll look into the 137/139 thing anyway and try to trace the new PC. I even removed and reinstalled the file sharing. No luck.

Got my other PC back so soon I'll be able to verify if the second PC can connect to the first PC.

Thinking I'll be doing a hard reset tonight -AND- rebuilding my laptop (HDD failure).

Lots of fun..

Thanks, I'll let you know how it goes for sure.

chuckcoger · 07-16-03, 07:29 PM

Maybe this will help as you trouble shoot this and give some insight into your problem.

NetBIOS name resolution occurs as follows on NT and win 98 and lower Devices

1. The client computer checks it's NetBIOS name cache
2. if a WINS (NetBIOS name server)server is available, the computer makes three attempts to contact it.
3. If a WINS server is unavailable, the computer makes three broadcasts on it's subnet for the name
4. If broadcasting fails then the client consults its local LMHOSTS file if it is available
5. If the NetBIOS name is not resolved through LMHOSTS, the client checks it's HOSTS file
6. Finally, the client computer tries to find a DNS server.
7. If the above steps fail, you get the computer not found message.

Today you can change the name resolution configuratio n to start at differnt nodes wheather it be the Broadcast, Peer, Mixed, or Hybrid node. This is done to prevent broadcast storms across large networks.

My question is and I truly dont know is does PocketPC differ and if so how?

Howard2k · 07-16-03, 08:44 PM

Yep, remember all that :-)

What I don't understand is:

1. Why it's a directed broadcast.
2. If it's name res, why can I not map by IP?
3. I'm using Pocket Hosts and the entries are in the registry...

So I'm not sure that it's name res. Thanks for the tips though.

Howard2k · 07-16-03, 08:49 PM

Hey Chuck,

Do you have a sniffer? Would you mind trying this and taking a capture and just let me know if you're seeing the same directed broadcast on 137 from the PPC?

Thanks.

chuckcoger · 07-18-03, 08:31 AM

I actually would have done this prior to posting the initial reply, however my wireless AP is, well smoked. I wont be getting another Linksys... so once I get the a new AP I will check it out.

Howard2k · 07-18-03, 09:54 AM

no prob. I've been out of time to troubleshoot it too. I'm off out of town for a few days so maybe I'll try and "cram" the fix tonight.

Drew_Mklasse · 07-26-03, 02:03 AM

Howard, did you manage to resolve your issues? I seem to be having the same ones as you regarding accessing shared drives.

BTW, nice to see a fellow Canuck on the boards :)