Accessing shares on wireless network

[Paul van Hagen]

Hello,

I'm trying to enable filesharing on my wireless home network.
Sofar, I've been able to enable this in one direction only. This is from the
non-browser elected to the browser elected machine. From the browser host to
the client it doesn't work.
Whatever I do, I don't get to see the shares in my network locations window.
I have verified the TCP/IP connection using ping at the cmd level and that
works with both the IP address and the computer system name. If I try to
access the share from Windows it complains "network not accessible or not
started". I have applied all troubleshooting tips from various sites
including the Microsoft support site. Still no luck.
Both clients are running Windows XP Home Edition SP2. I'm using a Linksys
wireless access point. Since I'm able to use file/print sharing in one
direction I assume changing the configuration on my Linksys router will not
help.

Appreciate any help.

Thanks.

 

[Chuck]

Hello,

I'm trying to enable filesharing on my wireless home network.
Sofar, I've been able to enable this in one direction only. This is from the
non-browser elected to the browser elected machine. From the browser host to
the client it doesn't work.
Whatever I do, I don't get to see the shares in my network locations window.
I have verified the TCP/IP connection using ping at the cmd level and that
works with both the IP address and the computer system name. If I try to
access the share from Windows it complains "network not accessible or not
started". I have applied all troubleshooting tips from various sites
including the Microsoft support site. Still no luck.
Both clients are running Windows XP Home Edition SP2. I'm using a Linksys
wireless access point. Since I'm able to use file/print sharing in one
direction I assume changing the configuration on my Linksys router will not
help.

Appreciate any help.

Thanks.

Paul,

Not knowing what sites are included in "various sites", I will offer my detailed
troubleshooting guide. Maybe there's a detail in there that hasn't occurred to
you.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html

You are correct in that since you have file sharing in one direction, you
obviously have connectivity OK. The router, which provides connectivity between
the computers on your LAN is essentially a switch - there are no settings that
are relevant to your problem.

If no help yet, provide "browstat status" and "ipconfig /all" from each
computer, and we can diagnose the problem. Read this article, and linked
articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

 

[Paul van Hagen]

Chuck,

Thanks for your offer to assist in further diagnosing this problem.

Following the information you requested using browstat and ipconfig/all.

Client1:

Output from ipconfig/all

Windows IP-configuratie

Host-naam . . . . . . . . . . . .: MARSHAPC

Primair DNS-achtervoegsel. . . . .:

Knooppunttype . . . . . . . . . . : hybride

IP-routering ingeschakeld. . . . .: nee

WINS-proxy ingeschakeld . . . . . : nee DNS-achtervoegselzoeklijst. . . . :
wanadoo.nl Ethernet-adapter Draadloze netwerkverbinding 4: Verbindingsspec.
DNS-achtervoegsel: wanadoo.nl

Beschrijving . . . . . . . . . . .: Linksys Wireless-G PCI Adapter with
SpeedBooster

Fysiek adres. . . . . . . . . . . : 00-0F-66-6D-02-6C

DHCP ingeshakeld. . . . . . . . . : ja

Autom. configuratie ingeschakeld. : ja

IP-adres. . . . . . . . . . . . . : 192.168.1.101

Subnetmasker. . . . . . . . . . . : 255.255.255.0 Standaardgateway. . . . .
.. . . . : 192.168.1.1 DHCP-server . . . . . . . . . . . : 192.168.1.1

DNS-servers . . . . . . . . . . . : 194.134.5.5 194.134.0.97

Lease verkregen . . . . . . . . . : donderdag 29 december 2005 15:49:35
Lease verlopen . . . . . . . . . : vrijdag 30 december 2005 15:49:35

Output from browstat status

Status for domain THUIS on transport
\Device\NetBT_Tcpip_{0FD41CF6-F664-4E79-B08B-74875B673738}

Browsing is active on domain.

Master browser name is: HOMEPCVANHAGEN

Could not connect to registry, error = 53 Unable to determine build of
browser master: 53

\\\\HOMEPCVANHAGEN. Version:05.01 Flags: 51203 NT POTENTIAL MASTER

1 backup servers retrieved from master HOMEPCVANHAGEN

\\HOMEPCVANHAGEN

There are 2 servers in domain THUIS on transport
\Device\NetBT_Tcpip_{0FD41CF6-F664-4E79-B08B-74875B673738}

There are 1 domains in domain THUIS on transport
\Device\NetBT_Tcpip_{0FD41CF6-F664-4E79-B08B-74875B673738}





Client2:

Windows IP-configuratie

Host-naam . . . . . . . . . . . .: HOMEPCVANHAGEN

Primair DNS-achtervoegsel. . . . .:

Knooppunttype: . . . . . . . . . .: onbekend

IP-routering ingeschakeld. . . . .: nee

WINS-proxy ingeschakeld . . . . . : nee

DNS-achtervoegselzoeklijst. . . . : wanadoo.nl

Ethernet-adapter Draadloze netwerkverbinding 2:

Verbindingsspec. DNS-achtervoegsel: wanadoo.nl

Beschrijving . . . . . . . . . . .: Linksys Wireless-G PCI Adapter with
SpeedBooster

Fysiek adres. . . . . . . . . . . : 00-0F-66-6D-03-59

DHCP ingeshakeld. . . . . . . . . : ja

Autom. configuratie ingeschakeld. : ja

IP-adres. . . . . . . . . . . . . : 192.168.1.100

Subnetmasker. . . . . . . . . . . : 255.255.255.0

Standaardgateway. . . . . . . . . : 192.168.1.1

DHCP-server . . . . . . . . . . . : 192.168.1.1

DNS-servers . . . . . . . . . . . : 194.134.5.5 194.134.0.97

Lease verkregen . . . . . . . . . : donderdag 29 december 2005 10:04:18

Lease verlopen . . . . . . . . . : vrijdag 30 december 2005 10:04:18

Status for domain THUIS on transport
\Device\NetBT_Tcpip_{C3BE99C7-8487-4AFE-A108-B34113BEAD0F}

Browsing is active on domain.

Master browser name is: HOMEPCVANHAGEN

Master browser is running build 2600

1 backup servers retrieved from master HOMEPCVANHAGEN

\\HOMEPCVANHAGEN

There are 2 servers in domain THUIS on transport
\Device\NetBT_Tcpip_{C3BE99C7-8487-4AFE-A108-B34113BEAD0F}

There are 1 domains in domain THUIS on transport
\Device\NetBT_Tcpip_{C3BE99C7-8487-4AFE-A108-B34113BEAD0F}

The "error 53" on client 1 is indeed looks suspicious. I have read your
article on the "Error 53" problem and I have applied all fixes suggested
there (including the LSP/WinSock fixes). However, I only applied them on
client 1 assuming that's where the problem is. I have also uninstalled my
virus and internet security software to make sure there is no firewall still
active in the background although the configuration mentioned it was
disabled. Still no luck! I keep getting the Error 53 message.

Further assistance is much appreciated.

Thanks!