Home network setup - can only PING in one direction and it's nothing obvious...

R

ricks.web.tat

Hi. I want to set up a home wireless network, two laptops, one used as
a gateway to the web for the other. However can only get them to ping
in one direction.

There is no physical problem (see below). However although the routing
and IP address seem fine to me I can not establish a link. What could
prevent an IP address being detected on the same subnet? And how do I
remedy this?

I manually configured the IP addresses on both machines to the normal
default, disabled firewalls etc. Machine A is a work machine and part
of a work domain. Machine B is a home machine and part of a workgroup.
I can not however see how this would affect the TCP/IP operation and
pinging.

Machine A machine B ISP
Work notebook home notebook ISP server
Onboard WAN------WAN card
USB modem --------Server
OS: XP profesional XP professional
IP: 192.168.0.2 192.168.0.1
Gateway: 192.168.0.2 192.168.0.1
Default gateway: 192.168.0.1 not specified
Net view \\pc reply sys error 53 sys error 5 (yes, 5, not 53)

Machine B can ping machine A
Machine A can not ping machine B
Firewalls disabled.
Before firewalls were disabled the incoming packets for handshaking
were detected and not blocked.
Machine A is set up to auto syncronise with a server on it's domain
and has various security behaviours imposed on it by the network admin,
e.g. the 'system' option in control panel has been disabled.

So physical link intact. In fact, under ' network connections' on
machine A in the 'wireless network connection status' there is high
signal strength and connection to the network of the wireless AP
running on machine B. I have selected the 'support' tab and
clicked 'repair' - no change.

Machine B is using an ASUS PCMCIA WAN card, with an asus soft AP
package (ASUS WAN control centre). All the settings are for open
network authentification, no encryption, no MAC addresses blocked, etc.

Although I can ping machine A from B, if I type \\192.168.0.2\ I get no
joy. 'Net view' does not return any link to the other machine.

Previously I have connected the two machines with a crossover cable,
which also had very limited connectivity. Although not 100% sure I
believe the system behaved exactly the same (definitely did not get
past the failure to ping issue).

Is there an app that will return a list of any firewalls/virus
checkers, incase I have missed anything?

I have run through a few options listed at www.howtonetworking.com/.
Note something I find weird - machine B will ping machine A however
returns sys error 5 in a net view lookup, why return a permissions
error when you can ping the device?

'client for microsoft networks' checked on both NICs.
I have tried installing the NetBIOS protocol on both machines, again no
change.
I have checked that the 'server' service is running.

As you can guess, any help much appreciated....
 
C

Chuck

Hi. I want to set up a home wireless network, two laptops, one used as
a gateway to the web for the other. However can only get them to ping
in one direction.

There is no physical problem (see below). However although the routing
and IP address seem fine to me I can not establish a link. What could
prevent an IP address being detected on the same subnet? And how do I
remedy this?

I manually configured the IP addresses on both machines to the normal
default, disabled firewalls etc. Machine A is a work machine and part
of a work domain. Machine B is a home machine and part of a workgroup.
I can not however see how this would affect the TCP/IP operation and
pinging.

Machine A machine B ISP
Work notebook home notebook ISP server
Onboard WAN------WAN card
USB modem --------Server
OS: XP profesional XP professional
IP: 192.168.0.2 192.168.0.1
Gateway: 192.168.0.2 192.168.0.1
Default gateway: 192.168.0.1 not specified
Net view \\pc reply sys error 53 sys error 5 (yes, 5, not 53)

Machine B can ping machine A
Machine A can not ping machine B
Firewalls disabled.
Before firewalls were disabled the incoming packets for handshaking
were detected and not blocked.
Machine A is set up to auto syncronise with a server on it's domain
and has various security behaviours imposed on it by the network admin,
e.g. the 'system' option in control panel has been disabled.

So physical link intact. In fact, under ' network connections' on
machine A in the 'wireless network connection status' there is high
signal strength and connection to the network of the wireless AP
running on machine B. I have selected the 'support' tab and
clicked 'repair' - no change.

Machine B is using an ASUS PCMCIA WAN card, with an asus soft AP
package (ASUS WAN control centre). All the settings are for open
network authentification, no encryption, no MAC addresses blocked, etc.

Although I can ping machine A from B, if I type \\192.168.0.2\ I get no
joy. 'Net view' does not return any link to the other machine.

Previously I have connected the two machines with a crossover cable,
which also had very limited connectivity. Although not 100% sure I
believe the system behaved exactly the same (definitely did not get
past the failure to ping issue).

Is there an app that will return a list of any firewalls/virus
checkers, incase I have missed anything?

I have run through a few options listed at www.howtonetworking.com/.
Note something I find weird - machine B will ping machine A however
returns sys error 5 in a net view lookup, why return a permissions
error when you can ping the device?

'client for microsoft networks' checked on both NICs.
I have tried installing the NetBIOS protocol on both machines, again no
change.
I have checked that the 'server' service is running.

As you can guess, any help much appreciated....

This still looks like a personal firewall problem. What firewalls did you
disable?
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html

And you say you installed NetBIOS? Or NetBEUI? You install the latter. You
activate the former. You SHOULD uninstall NetBEUI, and activate NetBIOS Over
TCP.
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html
<http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html>
http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html

And look at LSP / Winsock corruption.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

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

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top