Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

XP weird LAN trouble 1

Status
Not open for further replies.

ApocCrow

Technical User
May 4, 2003
6
AR
Hi
I´ve got three computers on a LAN. one with Windows XP (let´s call it Computer 1), other with Win98 (computer 2) and a third with XP (computer 3).
Now this is the problem: Computer 1 can see computer 2 and 3 but cannot access neither of them nor ping their IPs. Both computer 2 and 3 can see computer 1 but they can´t access it nor ping computer 1´s IP.
I assume as everybody can see each other, that the cable is right as is the NIC card, so, how can I solve this problem?
btw, computer 2 and 3 work fine between each other.

I would truly appreciate any help that you may provide me as I´ve been a week network-less and I NEED this thing working. PLEASE!!! :)
Again, thanks for any help that you may provide.
 
The problem is likely a firewall on XP #1. When it pings computers #2 or #3 the ping succeeds but it is blocked from seeing the response. Similarly when #2 or #3 ping XP Computer #1 the ping request is blocked by the firewall.

XP comes with a firewall by default. Make sure it is disabled. If you use any other firewall product many use a service that continues to run as a process even after the firewall is told to be disabled. The only sure way to make sure these firewalls are not causing a problem with ICMP traffic is to use MSCONFIG to disable them from the startup menu and reboot.

Two other known blocks to pings:

. If computer #1 has bridging enabled, or is set up to be a VPN endpoint it may not respond to a ping request;

. If you are connected through a hub, manually set all of your NICs to 10 T and half duplex. If you are connected to an autosensing router there is a good chance they are not autosensing correctly. Manually set the NICs to 100 - Full Duplex.

 
First, thanks for the help, I was REALLY needing it.
I'd like to ask you some questions about the possible solutions you gave me:
- about the firewall, is it the Internet Connection Firewall that you mean? If it is, I think it's off but how do I check that for sure?
(btw, no other firewall products installed)
- what's the bridging and how do I disable it if it's on?
- about the HUB thing, I'm not connected thru a HUB, I'm using "T" connectors to make a circle between all computers.
- The autosensing thing is the one on the IPX/SPX only? (btw, changing that thing seemed to change things a bit but not fix them, ie: for #1, making #2 invisible but not #3 but none of them accessible or pingable anyway)
-How do I know which one should I take? (Ethernet 802.2, 802.3, SNAP or II)
-The full duplex/half duplex and speed changes are the ones on the NIC card advanced config?; how do I change that setting on Win 98?

Oh, and some things I forgot to mention:
-#1 can ping localhost and 127.0.0.1
-All drives in all computers are shared

Again, thanks for the help.
 
Sounds like you're running 2 protocols: TCP/IP and IPX/SPX.

IPS/SPX is probably set up correctly (as the PCs can "see" each other).

Pings are TCP/IP specific. My guess is that TCP/IP just isn't set up properly.

If you have ANY firewall enabled, disable it (at least, whilst you are troubleshooting the problem).

I'm guessing since you refer to "T" connectors you have a BNC co-ax cabled network (not Cat5 cables).

BNC cable picture: Cat5 cable picture:
Do "ipconfig /all" on each of the PCs and post the results.

All your PCs should share a common IP configuration:
e.g. IP: 192.168.0.x (x between 2 and 250) subnet mask 255.255.255.0, specify a gateway IP if you have one.

hope some of this helps.

<marc> i wonder what will happen if i press this...[pc][ul][li]please give feedback on what works / what doesn't[/li][li]need some help? how to get a better answer: faq581-3339[/li][/ul]
 
You say that you are using 'T' pieces to make a RING??

if so then then you must be using co-ax (10base2) 50ohm cable. Connecting the ends back to each other to form a RING IS INCORRECT!!!!!!!!!!

A coaxial network should be connected as a BUS not a RING and should be correctly terminated at both ends (with a 50ohm terminator)
 
The XP Firewall can be found by right-clicking the network tray icon, Open Network Connection, right-click the Local Area Network Connection, Properties, Advanced. Uncheck the firewall setting if enabled on any machine.

Under the General tab, configure, Advanced, set all machines to a speed of 100 Full Duplex.

Under the General tab, get rid of IPX/SPX, you do not need it. Highlight TCP/IP, Properties:

Set the first machine to a static IP of 192.168.1.1, the second to a static IP of 192.168.1.2 and the third to a static IP of 192.168.1.3.

Then the Advanced button, WINS tab and uncheck LMHOSTS and check to enable Netbios over TCP/IP.

Make sure everyone has a unique name. Make sure everyone is a member of a Workgroup. Make sure the Workgroup name is identical on all three machines.

For the wiring as guestgulkin said you cannot do a true ring for the three machines. All machines need a T connector, and the 1st and Last machine need a terminating resistor on the open tap of the T. This by spec should be grounded on one end, either First or Last computer, to an earth ground.



 
Oops, right.. sorry, I didn´t think it enough when said that if formed a ring, it´s true, they´re connected linealy with terminators on each. In fact, they´re not 3 comps but 4 in the network but I didn´t include this last one because it didn´t add anything new and however did not check anything with this one.
btw, the cable looks like the BNC one.

I´ll try all you said and tell you what happens, also will do an IPconfig /all in all comps and post back.

Thank you all for the support!!
 
In fact, now that I remember, the #1 seen all the other comps even before of having the IPX/SPX protocol, I´ve added it to see if that made anything better (because both #2 and #3 have it installed) also installed NetBEUI (same reason) but the only protocols it had when it worked were TCP/IP, the QoS dunnowhat and MS client (the ones that come by default with XP). Also when things crew up too much, the Assistant for LAN connection seems sometimes of help
 
On all computers:
Client for Microsoft Networks
File and Printer Sharing
TCP/IP

(Ignore QoS, just uncheck it)

Under TCP/IP Properties:

A unique static IP address
Under Advanced, WINS Netbios over TCP/IP enabled
 
Will do, but... the net works ok for the rest of the computers.. do I need to do that on all comps? I wouldn´t like to screw what´s left of my network... unless NECESSARY to fix Computer #1´s network connection..
 
If it ain't broke, then don't fix it.

But IPX/SPX is unnecessary. Windows is fine with using Netbios to resolve names to addresses and show the other computers on the network. And fewer protocols generally is desirable because its faster.

You might see these two sites for both excellent advice in general about Windows networking, but as well checklists of things to look at on your network:

 
Congratulations guys!!! my network is fixed!! Thanks to everybody who offered help and solutions and very specially bcastner who kept following me until the end. The static config works pretty much fine.
Again, thanks for the help both technically and for giving me faith in the possibility that it would ever work again :]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top