Home Networking - Wired vs Wireless Issue

[mmogul]

Home Networking Problem

I have a home network with multiple computers – some wireless, some wired. Here is my issue.

Computer A is wireless. It can “see” Computer B – wired and Computer C – wired. However, Computer B and C cannot see Computer A. Both C and B can ping A by IP address but cannot ping by computer name.

But here’s the interesting part. If I connect Computer A to the network wired, then C and B can see Computer A and can ping by computer name.

I cannot figure out what the wireless factor has to do with this. Could it be a router problem?

Anyone?

 

[Freestone]

In properties for the Wireless adapter:

o Is File and Printer Sharing for Microsoft Networks enabled ?

o TCP/IP Properties, Advanced, WINS, is NetBIOS over TCP/IP enabled?

You should be able to compare the settings for the wired and wireless adapters to see what, if any, settings are different.

 

[linney]

I agree with "Freestone", here are some other troubleshooting MSKB in case you need them.

Update to the new XP Wireless Client:

http://support.microsoft.com/?kbid=917021

How to troubleshoot wireless network connections in Windows XP

http://support.microsoft.com/kb/313242/EN-US/?FR=1

How to troubleshoot wireless network connections in Windows XP Service Pack 2

http://support.microsoft.com/kb/870702/en-us?FR=1&PA=1&SD=HSCH

 

[themrspeedoist]

Like I tell all my employees; why get a wireless at all? When you are at home you have all the options of every ounce of speed your internet service provides. This may not be important and the thrill of being able to tarry around without a wire excites you then try getting all of the speed the non-wireless achieves.
Besides wireless does not impress me when on the other hand the non-wireless achieves three times the speed then the wireless. Faster for downloads, uploads whatever (mainline routers) are the way man, unless there just is no other good way then stick to non-wireless. Here is another reason a wireless is not GOOD for home use. Anybody has the ability to hack right into ALL of your hard drive, literally from any where on earth by leaps and bounds easier when you are using a wireless. Oh I know your next door neighbor has to have the password. BUT not 100% of your neighbors have to. A 12 year old can hack your computer as easy as a man falling off a log backwards. And we don't want this do we? I agree the wireless has it's place and the home is certantly not this place. REMEMBER SUCURITY. I know you are safer now if you understand what I and most of my colleagues already understand. I gave you this one. HAPPY HOLIDAYS

 

[mmogul]

Thanks for all the responses:

to freestone: file and printer sharing is enabled. Netbios over tcp/ip is set to "default" -- the same setting as wired. I will try setting it to "enable netbios over tcp/ip" to see if it makes a difference. I'll let you know -- doubtful it will have an effect since wired is configured the same as wireless.

to: linney: thanks for the links. I'll review them and let you know if I get any results.

to: themrspeedoist: I respectfully disagree. Wireless is in fact more useful at home than at work. At work, I tend to be working at one place. At home, I want to work in my home office, at the kitchen table, look up something on my laptop while sitting in front of the tv. This is without any consideration of the difficulties of running ethernet throughout an 85 year old house. The benefits of wireless outweigh the negligible risk of a 12 year old hacking into my system. You know, people can steal my car too. But I still drive one.

 

[BadBigBen]

if the suggestions do not prove fruitful, then I would look at the ROUTER...

since I do not know which router you are using... some have certain settings which allow communication between wired and wireless... and then there is the build in firewall, which can in fact hamper communication between wired and wireless...

and other routers do not allow communication between ETH and ATH at all...

Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

 

[mmogul]

I believe I have solved the issue. I resolved the problem by adding "NWLink IPX/SPX/NetBIOS Compatible Transport Protocol " to my network properties list on each computer of my network.

I found that on another forum to address a related issue and thought I would give it a try. I don't know why it works ... but at least for now, all computers can see each other.

Happy New Year!

 

[BadBigBen]

Glad you found the problem, and thank you for posting the fix aswell...

Happy New Year - Guten Rutsch

Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

 

[Freestone]

You have fixed the issue by adding another protocol on your network. While this allows communications between your networked PCs, it doesn't fix or answer why TCP/IP was not functioning properly.

 

[edfair]

In several cases I've run into, using the IP reset fix has cleaned out the problems. That, and a reboot.

 

[PRPhx]

mmogul:
It would be interesting to see what happened on each pc if
you did a ipconfig /release and /renew on each pc. Then reboot your pc's and the router.