PC can see 2 others on LAN but cannot be seen back

This is really weird. I am trying to set up an 802.11b 3 PC home LAN
consisting of
Desktop 1, XP home, adapter cabled to a router
Desktop 2, Win 98 SE, wireless adapter
Laptop, XP Home, wireless adapter

Desktop 1 can see all three PCs in Network Neighborhood, but cannot access
the other two. The other 2 PCs can only see themselves. File and printer
sharing is turned on, folders are shared, firewalls are turned off,
workgroup names are correctly set, etc.

1. What can be causing this weird behavior? When I use a cable from the
router to laptop, LAN works fine and files can be accessed in both
directions using NetBEUI.

2. Since NetBEUI works in the cabled LAN, why does it not work in the
wireless LAN I am trying to set up?

3. Could there be a "service" I may have turned off on some of the
computers?

Appreciate any help I can get. Thanks.

--

Jeff McPherson
Email address deliberately false to avoid spam
(E-Mail Removed)
Outgoing mail is certified Virus Free by AVG

My first impression is to make sure all computers have TCP/IP installed,
have all use same workgroup name, i.e., WORKGROUP, on XP machines, set
up home networking.

Jim
Cortez, CO

"Jeff Malka" <(E-Mail Removed)> wrote in message
news:8_wDb.39083$A%(E-Mail Removed)...
This is really weird. I am trying to set up an 802.11b 3 PC home LAN
consisting of
Desktop 1, XP home, adapter cabled to a router
Desktop 2, Win 98 SE, wireless adapter
Laptop, XP Home, wireless adapter

Desktop 1 can see all three PCs in Network Neighborhood, but cannot
access
the other two. The other 2 PCs can only see themselves. File and printer
sharing is turned on, folders are shared, firewalls are turned off,
workgroup names are correctly set, etc.

1. What can be causing this weird behavior? When I use a cable from the
router to laptop, LAN works fine and files can be accessed in both
directions using NetBEUI.

2. Since NetBEUI works in the cabled LAN, why does it not work in the
wireless LAN I am trying to set up?

3. Could there be a "service" I may have turned off on some of the
computers?

Appreciate any help I can get. Thanks.

--

Jeff McPherson
Email address deliberately false to avoid spam
(E-Mail Removed)
Outgoing mail is certified Virus Free by AVG

"Jeff Malka" <(E-Mail Removed)> wrote in
news:8_wDb.39083$A%(E-Mail Removed):

> This is really weird. I am trying to set up an 802.11b 3 PC home LAN
> consisting of
> Desktop 1, XP home, adapter cabled to a router
> Desktop 2, Win 98 SE, wireless adapter
> Laptop, XP Home, wireless adapter
>
> Desktop 1 can see all three PCs in Network Neighborhood, but cannot
> access the other two. The other 2 PCs can only see themselves. File
> and printer sharing is turned on, folders are shared, firewalls are
> turned off, workgroup names are correctly set, etc.
>
> 1. What can be causing this weird behavior? When I use a cable from
> the router to laptop, LAN works fine and files can be accessed in both
> directions using NetBEUI.
>
> 2. Since NetBEUI works in the cabled LAN, why does it not work in the
> wireless LAN I am trying to set up?
>
> 3. Could there be a "service" I may have turned off on some of the
> computers?
>
> Appreciate any help I can get. Thanks.
>

Your best bet is to switch the Network Protocol over to NWlink NetBios
Compatible on all machines instead of NetBeui. You should first uninstall
Netbeui before installing NWlink NetBios, otherwise, you'll hose the
TCP/IP Stack on the machine, which is an easy fix if that happens.

I don't know why. But NETbeui and wireless, especially with WEP enabled
don't play well together. I could never get the machines to access each
other with NETbeui. Wire to wire machine connection was OK but not wire
to wireless or wireless to wire. I don't know about wireless to wireless,
it may be the same situation.

Duane

Thanks Duane.

> Your best bet is to switch the Network Protocol over to NWlink NetBios
> Compatible on all machines instead of NetBeui. You should first uninstall
> Netbeui before installing NWlink NetBios, otherwise, you'll hose the
> TCP/IP Stack on the machine, which is an easy fix if that happens.

I originally installed Net BEUI because that was the only way I could get
the LAN working when cabled. I suppose I could use "System Restore" to
switch back to where I was should NWlink NetBios make the cabled LAN no
longer work. Do you think System restore will restore things should I get
in trouble? Hate to lose the LAN when cabled :-(

--

Jeff McPherson
Email address deliberately false to avoid spam
(E-Mail Removed)
Outgoing mail is certified Virus Free by AVG

"Duane Arnold" <(E-Mail Removed)> wrote in message
news:Xns945335AF245FBdarnold92insightbbco@204.127. 204.17...
> "Jeff Malka" <(E-Mail Removed)> wrote in
> news:8_wDb.39083$A%(E-Mail Removed):
>
> > This is really weird. I am trying to set up an 802.11b 3 PC home LAN
> > consisting of
> > Desktop 1, XP home, adapter cabled to a router
> > Desktop 2, Win 98 SE, wireless adapter
> > Laptop, XP Home, wireless adapter
> >
> > Desktop 1 can see all three PCs in Network Neighborhood, but cannot
> > access the other two. The other 2 PCs can only see themselves. File
> > and printer sharing is turned on, folders are shared, firewalls are
> > turned off, workgroup names are correctly set, etc.
> >
> > 1. What can be causing this weird behavior? When I use a cable from
> > the router to laptop, LAN works fine and files can be accessed in both
> > directions using NetBEUI.
> >
> > 2. Since NetBEUI works in the cabled LAN, why does it not work in the
> > wireless LAN I am trying to set up?
> >
> > 3. Could there be a "service" I may have turned off on some of the
> > computers?
> >
> > Appreciate any help I can get. Thanks.

Thank you so much for replying.

1. They all have TCP/IP installed with the correct IP addresses
2. all have the same workgroup. The workgroup appears in all three - but
within the workgroup only one PC sees all three PCs in the workgroup. The
others only show themselves within it. The desptop that shows all three can
on ly access itself when on wireless. When cabled (with NetBEUI) it can
access the other PCs.
3. Home networking was set up when I had the cabled network using NetBEUI.
Should it be re-setup again for the wireless?

On the laptop XP Home, there is a Toshiba utility called "ConfigFree" which
shows the wireless LAN having the following possible problems between the
laptop and the router:
a) "There is no response from the DNS server"
b) "There is no response from the default gateway"

Trouble is I do not know what to do with this information. I checked and
a) the SSID is the same on all three
b) TCP/IP settings has the following checked
Obtain an IP address automatically
Obtain DNS server address automatically
Alternate Configuration: Automatic private IP address (maybe I should
use "user configured to force it to see the LAN?)

--

Jeff McPherson
Email address deliberately false to avoid spam
(E-Mail Removed)
Outgoing mail is certified Virus Free by AVG

"Jimmy" <(E-Mail Removed)> wrote in message
news:TAxDb.6466$(E-Mail Removed) k.net...
> My first impression is to make sure all computers have TCP/IP installed,
> have all use same workgroup name, i.e., WORKGROUP, on XP machines, set
> up home networking.
>
> Jim
> Cortez, CO
>
> "Jeff Malka" <(E-Mail Removed)> wrote in message
> news:8_wDb.39083$A%(E-Mail Removed)...
> This is really weird. I am trying to set up an 802.11b 3 PC home LAN
> consisting of
> Desktop 1, XP home, adapter cabled to a router
> Desktop 2, Win 98 SE, wireless adapter
> Laptop, XP Home, wireless adapter
>
> Desktop 1 can see all three PCs in Network Neighborhood, but cannot
> access
> the other two. The other 2 PCs can only see themselves. File and printer
> sharing is turned on, folders are shared, firewalls are turned off,
> workgroup names are correctly set, etc.
>
> 1. What can be causing this weird behavior? When I use a cable from the
> router to laptop, LAN works fine and files can be accessed in both
> directions using NetBEUI.
>
> 2. Since NetBEUI works in the cabled LAN, why does it not work in the
> wireless LAN I am trying to set up?
>
> 3. Could there be a "service" I may have turned off on some of the
> computers?
>
> Appreciate any help I can get. Thanks.
>
> --
>
> Jeff McPherson
> Email address deliberately false to avoid spam
> (E-Mail Removed)
> Outgoing mail is certified Virus Free by AVG
>
>
>
>

"Jeff Malka" <(E-Mail Removed)> wrote in
news:hYCDb.39084$A%(E-Mail Removed):

> Thanks Duane.
>
> I originally installed Net BEUI because that was the only way I could
> get the LAN working when cabled. I suppose I could use "System
> Restore" to switch back to where I was should NWlink NetBios make the
> cabled LAN no longer work. Do you think System restore will restore
> things should I get in trouble? Hate to lose the LAN when cabled :-(
>


The only reason it won't work is becuase the machine got a 169.xxx IP
due to the machine not being able to release the 169.xxx IP that the
TCP/IP Stack is using.

The 169.xxx IP is an Auto Config IP assgined by the O/S when it cannot
obtain a vaild IP from a DHCP server. In the case of the machine with
169.xxx IP the machine will not be able to access the Internet, but it
can access other machines on a LAN and the other machines can access it.

The solutions below are for a Win 9.X O/S and getting that 169.xxx on any
O/S the solutions may not fix the issues, which will have to be tracked
down as to the cause and a appropriate soultion found.

But in your case, it should get you out of trouble without having to do a
system restore.

1) rebbot the machine to see if it will release the 169.xxx IP and can be
done on XP too.

2) You can try issuing IPCONFIG /Release and IPCONFIG /renew at the
command prompt to see if the machine can obtain a valid IP and can be
done on XP too.

3) You can use the utility below.

http://www.bu.edu/pcsc/internetaccess/winsock2fix.html

4) If all else fails and the 169.xxx number will not be released by the
O/S or you cannot access the Internet, then you can take five minutes and
rebuild the TCP/IP stack on the machine by using REGEDIT.

a) go to HKLM\System\CurrentControlSet\Services
b) delete the Winsock and Winsock2 entries
c) go to the NIC's Property Box and uninstall all services and protocols
d) reboot the machine which will rebuild the Stack
e) install the services and protocols back in the NIC's Property Box.


For XP the following:

1) Use the procesure below

http://www.petri.co.il/reinstall_tcp_ip_xp.htm

2) Step 4A above

3) reboot the machine

4) Step 4E


You can use 4A through 4E as well on Win NT and 2K when all else fails.

On the link above, there are other What's Related? solutions.

Just make sure you uninstall the current protocol first before you
install the other one, and you won't have to implement any of it.

Duane

I just found something (on the laptop with the built in wireless trying to
see the desktop cabled to the router) that might explain my problems. Maybe
this will provide a clue to what is wrong in my setup.

When I click on Network setup Wizard, I come to a screen titled:
"The wizard found disconnected network hardware". The only connection it
shows is the NIC for the cable connection (which is of course disconnected
as I am trying to setup the wireless). The problem is that it does not show
the wireless connection even though it is on and the strength is excellent!

Could that be the problem? That the wireless NIC is not setup properly (even
though it came pre-installed with the laptop) so that XP does not see it as
"available" for a LAN? Yet when I open Network Connections, I see under the
section labeled "LAN or High-Speed internet" that there are 2 entries, one
for
1. Wireless Network Connection, enabled, Toshiba Wireless LAN Mini PCI ...
(when clicked on it says: connected, 11.0 Mbps, strength excellent,
sent 469, received 0)
2. Local Area Connection, Network cable unplugged, etc.

--

Jeff McPherson
Email address deliberately false to avoid spam
(E-Mail Removed)
Outgoing mail is certified Virus Free by AVG

"Duane Arnold" <(E-Mail Removed)> wrote in message
news:Xns945335AF245FBdarnold92insightbbco@204.127. 204.17...
> "Jeff Malka" <(E-Mail Removed)> wrote in
> news:8_wDb.39083$A%(E-Mail Removed):
>
> > This is really weird. I am trying to set up an 802.11b 3 PC home LAN
> > consisting of
> > Desktop 1, XP home, adapter cabled to a router
> > Desktop 2, Win 98 SE, wireless adapter
> > Laptop, XP Home, wireless adapter
> >
> > Desktop 1 can see all three PCs in Network Neighborhood, but cannot
> > access the other two. The other 2 PCs can only see themselves. File
> > and printer sharing is turned on, folders are shared, firewalls are
> > turned off, workgroup names are correctly set, etc.
> >
> > 1. What can be causing this weird behavior? When I use a cable from
> > the router to laptop, LAN works fine and files can be accessed in both
> > directions using NetBEUI.
> >
> > 2. Since NetBEUI works in the cabled LAN, why does it not work in the
> > wireless LAN I am trying to set up?
> >
> > 3. Could there be a "service" I may have turned off on some of the
> > computers?
> >
> > Appreciate any help I can get. Thanks.
> >
>
> Your best bet is to switch the Network Protocol over to NWlink NetBios
> Compatible on all machines instead of NetBeui. You should first uninstall
> Netbeui before installing NWlink NetBios, otherwise, you'll hose the
> TCP/IP Stack on the machine, which is an easy fix if that happens.
>
> I don't know why. But NETbeui and wireless, especially with WEP enabled
> don't play well together. I could never get the machines to access each
> other with NETbeui. Wire to wire machine connection was OK but not wire
> to wireless or wireless to wire. I don't know about wireless to wireless,
> it may be the same situation.
>
> Duane

"Jeff Malka" <(E-Mail Removed)> wrote in
news:hfQDb.39097$A%(E-Mail Removed):

> I just found something (on the laptop with the built in wireless
> trying to see the desktop cabled to the router) that might explain my
> problems. Maybe this will provide a clue to what is wrong in my
> setup.
>
> When I click on Network setup Wizard, I come to a screen titled:
> "The wizard found disconnected network hardware".

1) The *dreaded* Network Wizard on XP is nothing but trouble. If you have
the Bridge ICON along with the NIC ICON in the Local Area Network
Connection screen, you should *delete* it. Don't use the Network Wizard
if you want to stay out of trouble.

2) Forget any utility that you are using for the config of the wireless
card on XP. Don't even install it as they don't play well with XP. You
should use XP's Device Manager to install the driver for the wireless
card and also config the card there too by right-clicking on the device
and going to Properties. You should have the driver for the card on its
install CD or you may have to go to the card's Website and download the
driver. You can get to the Device Manager by right-clicking on the MY
Computer line Properties off of the Start button.

3) Disable the Wireless Zero Configuration Service, which can also be
giving you problems. You can do this by going to Control Panel/Preform
and Maint/Admin Tools/Services and disable WZC.

4) On the NIC's Properties Box area, there is an option to show the
Active Connection, which will place the connection Icon in the Job Tray
next to the clock. You put the mouse on the Icon and the signal strength
will be shown to you.

I am not for sure about this but during my initial setup of my XP
machines I know I saw something about a special setup disk that had to be
made by XP's Network Wizard so that it could install stuff on a Win 9'x
machine so that the XP machine could access it. You may not need it at
all. I don't know.

You may still need to switch the network protocol over to NWlink on all
machines. The machines may be able to see each other, but it doesn't mean
they can access each other. I use NWlink on all my machines wired and
wireless and share resources between all of them.

HTH

Duane

First Duane, I want to thank you for taking the time to help me with this.
I truly appreciate it greatly.

I am now convinced and ill try NWLink tonight as you suggested. Just one
more question. Are there any greater security issues using NWLink rather
than the other network protocols? I've looked in books and can find no
information on NWLink to read up on :-((

Also, one of the 3 PCs I would like to link to, runs W98 SE. Is NWLink OK
for that too?

Thanks again.

--

Jeff McPherson
Email address deliberately false to avoid spam
(E-Mail Removed)
Outgoing mail is certified Virus Free by AVG

"Duane Arnold" <(E-Mail Removed)> wrote in message
news:Xns9453E4A59DB90darnold92insightbbco@204.127. 199.17...
> "Jeff Malka" <(E-Mail Removed)> wrote in
> news:hfQDb.39097$A%(E-Mail Removed):
>
> > I just found something (on the laptop with the built in wireless
> > trying to see the desktop cabled to the router) that might explain my
> > problems. Maybe this will provide a clue to what is wrong in my
> > setup.
> >
> > When I click on Network setup Wizard, I come to a screen titled:
> > "The wizard found disconnected network hardware".
>
> 1) The *dreaded* Network Wizard on XP is nothing but trouble. If you have
> the Bridge ICON along with the NIC ICON in the Local Area Network
> Connection screen, you should *delete* it. Don't use the Network Wizard
> if you want to stay out of trouble.
>
> 2) Forget any utility that you are using for the config of the wireless
> card on XP. Don't even install it as they don't play well with XP. You
> should use XP's Device Manager to install the driver for the wireless
> card and also config the card there too by right-clicking on the device
> and going to Properties. You should have the driver for the card on its
> install CD or you may have to go to the card's Website and download the
> driver. You can get to the Device Manager by right-clicking on the MY
> Computer line Properties off of the Start button.
>
> 3) Disable the Wireless Zero Configuration Service, which can also be
> giving you problems. You can do this by going to Control Panel/Preform
> and Maint/Admin Tools/Services and disable WZC.
>
> 4) On the NIC's Properties Box area, there is an option to show the
> Active Connection, which will place the connection Icon in the Job Tray
> next to the clock. You put the mouse on the Icon and the signal strength
> will be shown to you.
>
> I am not for sure about this but during my initial setup of my XP
> machines I know I saw something about a special setup disk that had to be
> made by XP's Network Wizard so that it could install stuff on a Win 9'x
> machine so that the XP machine could access it. You may not need it at
> all. I don't know.
>
> You may still need to switch the network protocol over to NWlink on all
> machines. The machines may be able to see each other, but it doesn't mean
> they can access each other. I use NWlink on all my machines wired and
> wireless and share resources between all of them.
>
> HTH
>
> Duane
>
>
>
>
>

OK, I took the plunge. I uninstalled NetBEUI and installed NWLink on both XP
PCs - but not much progress.

On the desktop (with a non-wireless NIC connected by cable to a DLink
wireless router), the workgroup when opened shows all 3 PCs, but can only
open itself, not the other two ("Network path not found").

On the Toshiba laptop with the built-in wireless "Search for computer name"
finds itself, but not the desktop. Also, in case this is useful info, when I
open the workgroup on it, it is empty: not even itself is in it.

Maybe I need to make certain adjustments to NWLink?

The 3rd PC that I wish to connect to the LAN is a desktop running W98 SE. I
could find no NWLink to install on it. Any suggestions?

--

Jeff McPherson
Email address deliberately false to avoid spam
(E-Mail Removed)
Outgoing mail is certified Virus Free by AVG