Forum Home
Press F1
 
Thread ID: 25785 2002-10-11 23:24:00 Networking question Callum Hey (283) Press F1
Post ID Timestamp Content User
88434 2002-10-13 02:38:00 > Callums first posting said backoffice could ping POS
> and get a response from it ...

That's something we've found odd - first we thought it did, but then we think it actually was pinging itself... and our final test it wouldn't ping anything :)

> Desperation mode:
> (1) Have you given them fixed IP numbers? ... in the
> same net (watch for dud masks). E.g., 192.168.0.1 and
> 192.168.0.2, mask 192.168.0.255 .

Tried both fixed and Windows assigned - got the same result

> (2) Should be able to ping 127.0.0.1 (that's
> always "me", "mycard".

Running "netconfig" and getting the local IP addresses, pinging that address timed out. Didn't try pinging 127.0.0.1 - will try that next :)

> (3) Have you tried another cable? Is it a
> crossover? (hold the plugs with cable at bottom,
> latch away from you ... the pin numbers are
> 1,2...7,8). Pin 1 goes to 3, 2 to 6, 3 to 1, 6 to 2
> in a crossover.

Yup - exactly the same result testing with another cable. The second cable we know definitely works, so we've ruled out the cable.

> (4) If "goodie" can see "baddie's" name, there must
> be some communication.

That's what we figured - some communication doesn't mean full communication though. We're waiting for it to come back from the guy at NL and see what his verdict is :D

> Conclusion: Networks are fun. :_|
>
> Idea: Have you got two copies of PC World's CD with
> Knoppix? That would probably be a good test of the
> hardware. Linux networks nicely ...

That's a good idea... might be worth a try

Mike.
Mike (15)
88435 2002-10-13 04:21:00 What errors is the ping giving you.

I had a error code 65 once. It was due to vsmon running when I thought I'd disabled ZA.
-=JM=- (16)
88436 2002-10-13 05:37:00 No error code - just "request timed out" - basically there was no answer.

No firewall running (not even the XP one).

Mike.
Mike (15)
88437 2002-10-13 06:16:00 Have you set up the users allowed to connect to the computer?

All the users on one computer have to be on the other one if you want them to be allowed to connect to one another.

If you're not getting a response from your NIC, try swapping it in another PCI slot and reinstalling it. If you still can't get a response you can switch it with the other computer and see if that computer has no problem with it. If it does... then it's most likely the NIC if it works... then you will have to figure out what is blocking is stopping it.
Kame (312)
88438 2002-10-13 07:37:00 > Have you set up the users allowed to connect to the
> computer?
> All the users on one computer have to be on the other
> one if you want them to be allowed to connect to one
> another.

Really??? I didn't know this :) even for admin users? (not logged in as admin, but using users with admin rights). They don't need to be logged in on the both though do they?

> If you're not getting a response from your NIC, try
> swapping it in another PCI slot and reinstalling it.

It's an onboard NIC, so can't put it in another slot... but we did reinstall drivers etc.

Mike.
Mike (15)
88439 2002-10-13 10:34:00 Sounds like a dodgy NIC to me, you might have to install another in a PCI slot just to prove it. NIC cards arwn't too expensive but it is a pain I know, sometimes you have to do it for your own piecw of mind.
i had a prob recently where pinging worked but couldn't browse the network shares, getting the subnetmask the same solbved the prob

the answer is ~42~
~42~ (2034)
1 2