timeout or unreachable

[Robert_L]

I am still having pinging probs and wonder if someone would test something for me. Assuming you have 2 computers connected via crossover cable and you disconnect the cable, what is the "error message" be if you try to ping your other computer:

"destination host unreachable"

or

"timed out"

I have been told it should be a timeout which would indicate the problem is with my configuration since I'm getting "destination host unreachable" when I disconnect the cable and ping.

Thanks,
Robert_L

[prince_kenshi]

It doesn't say anything. It just keeps trying to ping until I break it. But it sounds like you have a routing problem. That's usually what that message means.

[Xsecrets]

Ok here we go destination host unreachable would happen for a couple of reasons. First if you are using a domain name. (linuxnewbie.org) and you don't have your dns set up properly it can't resolve that to and IP address. I'm guessing your using ip addresses to ping so this is probably not the problem. second if the two addresses are not on the same subnet and you don't have a gateway set. this could be your problem. you need to make sure they are both on the same subnet (192.168.0.1 192.168.0.2) and that they both have the same subnet mask (255.255.255.0) these addresses are of course just examples and can be changed for your situation. when the computer gets an IP address it does an opperation called anding with the subnet mask to determine if that adress is on it's same subnet and if it is it does a broadcast if not it sends tries the gateway.

[Robert_L]

Thanks for your trying it prince_k. I guess my networking config. on this machine is messed up. Perhaps from experimenting with the "hoo
stname" command a while back, though dialup is working fine and no other obvious problems.
I have been trying so long to fix this I think I should probably reinstall all the network stuff, though this may not help as I think internal addresses are needed and set whether you install networking stuff or not. Then i will either "find a way to fix it" or reinstall. I wish there was a new version of mandrake coming out so I would have an excuse (or I had enough disk space to add another dist. as an experiment.)

Xsecrets,
My setup is exactly as you indicated in your example, same addresses and masks in fact. But if pulling out the crossover still gives me "unreachable" I am guessing that it is not about the compatibility of the two machines addresses but a problem local to my machine.
Thanks again,
Robert_L

[Robert_L]

thanks for your post,
This is the first I've heard that you can't use a crossover with 2 nicks in the machine serving the dsl feed. In fact that was suggested as the ONLY way of doing it.
Now I'm not sure if they are crossover after reading your discription, though I was sold it as such. Nothing rings a bell about pin-out or "both ends the same". Do you mean both ends as int he two plugs at either end of the cable. Don't see a pin-out whatever that is.
all the best,
Robert_L

[TheBrewMeister]

If your connectors are clear, you can see the wire colors to see if both ends are the same. I did try the crossover cable on my network with no success. I guess it could be something I did wrong. I have also had no luck with serving the connection through windows without using sygate.

[TheBrewMeister]

I did try disconnecting my cable from the windows98 machine and get the timeout message.

[prince_kenshi]

Crossover should work the same way as a hub. You should be able to share internet over it just the same.

Do check the color patterns on the plugs. There should be two pairs that are crossed for a crossover cable. I really need to memorize the color code. Also check your network settings. If it says that immediately, I'd say it's more likely a configuration problem. If you need to set it again, use netconfig rather than completely reinstalling.

[Xsecrets]

wo o wbl g wg bl wbr br
wg g wbl o wo bl wbr br

this would be the two ends on a crossover cable.

[TheBrewMeister]

I found this on making a cross-over cable. Might help you check the wires to see if it is correct. http://www.makeitsimple.com/how-to/dyi_crossover.htm

[Robert_L]

Thanks guys,
I have discovered that it is in fact a crossover cable. And in fact there is a tag on the cable where it is clearly written "crossover"-- missed it on first check. (still it was worth making sure)
However, even if it was not a c/o there would still be the "unreachable" problem that clearly tells me I have a screwup in my configuration somewhere,
especially after it was tested by several in this forum. Back to the drawing board.
all the best,
Robert_L