Networking experts I need help

[BriGy86]

make sure your using the right cables i.e. cross over and straight through in the right places

some nic's can auto detect what lines are sending and recieving, some can't, so that might be a problem once you switched them out

 

[mzkhadir]

Originally posted by: Citrix

Originally posted by: BriGy86
something that would also be helpful is the lay out of your "network"

internet connection to wifes computer to your comptuer to hub to other sh!t... what exactly is it?

a layout for 3 machines???

ok, mine connects to the ineternet via dialup. I share that connection with my wifes XP machine and until yesterday it has worked fine.

I have a 24 port Bay Networks 100mb hub that i just replaced with another

My wifes PC connects to the internet through the hub to my PC out to the cloud.

My little POS PC that i have as a file server is only used to connect to the shared drives on it.

I can not Ping, tracert, ipconfig /anything because i cant get ANY COMM across my wires.

My question is WHY!!!!! UGGGGG, by all rights I should be able to fricken ping my other machines.

C:\ping oinker
Ping request could not find host oinker. Please check the name and try again.


C:\ping 192.168.0.2

Pinging 192.168.0.2 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

what is your gateway ? Is your gateway set ?

 

[JoLLyRoGer]

1st rule of troubleshooting is to check your cables. Not trying to be Captain Obvious, but that includes the power cable to your hub. Have you tried pinging from one client machine to another to test out your hardware, or have you just tried pinging from your host (gateway) to your client boxes? Have you tried swapping in the old hardware (known good configuration), etc.

Seriously, don't overlook the small stuff.

Post back and LMK, Ok?

EDIT: Also, ask youself, "What changed between yesterday and today?" Start there..

 

[OutHouse]

I plugged in 192.168.0.1 for the gateway on my wifes machine and still can not ping.

 

[BriGy86]

some times its 192.168.1.1

 

[PlatinumGold]

Originally posted by: Citrix

Originally posted by: BriGy86
something that would also be helpful is the lay out of your "network"

internet connection to wifes computer to your comptuer to hub to other sh!t... what exactly is it?

a layout for 3 machines???

ok, mine connects to the ineternet via dialup. I share that connection with my wifes XP machine and until yesterday it has worked fine.

I have a 24 port Bay Networks 100mb hub that i just replaced with another

My wifes PC connects to the internet through the hub to my PC out to the cloud.

My little POS PC that i have as a file server is only used to connect to the shared drives on it.

I can not Ping, tracert, ipconfig /anything because i cant get ANY COMM across my wires.

My question is WHY!!!!! UGGGGG, by all rights I should be able to fricken ping my other machines.

C:\ping oinker
Ping request could not find host oinker. Please check the name and try again.


C:\ping 192.168.0.2

Pinging 192.168.0.2 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

ok, so you changed switches. that's the only thing you did differently?

then it would seem that your problem is with the switch. many switches allow you to switch between crossover to straight so that you can use the same basic cable as a crossover or a straight.

you want to make sure all those are set correctly?

does you xp pc indicate that you have a network connection?

 

[mzkhadir]

Originally posted by: Citrix
I plugged in 192.168.0.1 for the gateway on my wifes machine and still can not ping.

but your pc is .1, change your pc to .3 and then add the gateway to your machine of .1

 

[OutHouse]

Originally posted by: JoLLyRoGer
1st rule of troubleshooting is to check your cables. Not trying to be Captain Obvious, but that includes the power cable to your hub. Have you tried pinging from one client machine to another to test out your hardware, or have you just tried pinging from your host (gateway) to your client boxes? Have you tried swapping in the old hardware (known good configuration), etc.

Seriously, don't overlook the small stuff.

Post back and LMK, Ok?

EDIT: Also, ask youself, "What changed between yesterday and today?" Start there..

Done all that. Changed out my NIC, Changed out the HUB, Tested my wires with a Fluke tester i borrowed from work. Have good lights on NIC's and on HUB. Nothing has changed. Can not ping any machine from any machine. they are blind except for when i unplug the wire and windows has that popup that says the network was disconnected.

 

[PlatinumGold]

Originally posted by: Citrix
I plugged in 192.168.0.1 for the gateway on my wifes machine and still can not ping.

i'm beginning to think it's not a gateway issue. if it was just a gateway issue, you would still be able to ping.

first off, you aren't getting a dynamic ip address, so it's not just gateway.

2nd, we have to find out for sure that your physical connection is working. make sure all the lights are right etc.

3rd, i think you indicated that you changed out a switch. check to see if the switch has a straight to crossover button for any of or all of your connections.

 

[PlatinumGold]

btw, why did you change from hub to switch? for 2nodes i don't think it really makes any difference.

 

[JoLLyRoGer]

Originally posted by: PlatinumGold

Originally posted by: Citrix

Originally posted by: BriGy86
something that would also be helpful is the lay out of your "network"

internet connection to wifes computer to your comptuer to hub to other sh!t... what exactly is it?

a layout for 3 machines???

ok, mine connects to the ineternet via dialup. I share that connection with my wifes XP machine and until yesterday it has worked fine.

I have a 24 port Bay Networks 100mb hub that i just replaced with another

My wifes PC connects to the internet through the hub to my PC out to the cloud.

My little POS PC that i have as a file server is only used to connect to the shared drives on it.

I can not Ping, tracert, ipconfig /anything because i cant get ANY COMM across my wires.

My question is WHY!!!!! UGGGGG, by all rights I should be able to fricken ping my other machines.

C:\ping oinker
Ping request could not find host oinker. Please check the name and try again.


C:\ping 192.168.0.2

Pinging 192.168.0.2 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

ok, so you changed switches. that's the only thing you did differently?

then it would seem that your problem is with the switch. many switches allow you to switch between crossover to straight so that you can use the same basic cable as a crossover or a straight.

you want to make sure all those are set correctly?

does you xp pc indicate that you have a network connection?

To parrot the above poster and expand a bit, some hubs/switches are internally crossed over, some are internally straight-through, while others are selectable. This usually applies to the 'Uplink' port or port #1 on your hub/switch. For what you're trying to do I'd recommend using all straight-through cables and leave the 'Uplink' or #1 port out of the setup.

In fewer words, start with port #2 on your hub/switch.

 

[PlatinumGold]

Originally posted by: JoLLyRoGer

Originally posted by: PlatinumGold

Originally posted by: Citrix

Originally posted by: BriGy86
something that would also be helpful is the lay out of your "network"

internet connection to wifes computer to your comptuer to hub to other sh!t... what exactly is it?

a layout for 3 machines???

ok, mine connects to the ineternet via dialup. I share that connection with my wifes XP machine and until yesterday it has worked fine.

I have a 24 port Bay Networks 100mb hub that i just replaced with another

My wifes PC connects to the internet through the hub to my PC out to the cloud.

My little POS PC that i have as a file server is only used to connect to the shared drives on it.

I can not Ping, tracert, ipconfig /anything because i cant get ANY COMM across my wires.

My question is WHY!!!!! UGGGGG, by all rights I should be able to fricken ping my other machines.

C:\ping oinker
Ping request could not find host oinker. Please check the name and try again.


C:\ping 192.168.0.2

Pinging 192.168.0.2 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

ok, so you changed switches. that's the only thing you did differently?

then it would seem that your problem is with the switch. many switches allow you to switch between crossover to straight so that you can use the same basic cable as a crossover or a straight.

you want to make sure all those are set correctly?

does you xp pc indicate that you have a network connection?

To parrot the above poster and expand a bit, some hubs/switches are internally crossed over, some are internally straight-through, while others are selectable. This usually applies to the 'Uplink' port or port #1 on your hub/switch. For what you're trying to do I'd recommend using all straight-through cables and leave the 'Uplink' or #1 port out of the setup.

In fewer words, start with port #2 on your hub/switch.

i've seen switches where several of them have selectable straight to crossover ports. makes it kind of rough for someone who isn't familiar with them and accidently press one of the buttons.

 

[spidey07]

replace the cable with a known, working, good and tested cable.

You have a layer1 problem.

-edit- link lights tell you nothing and do not mean the cable is good.

If you cannot operat at layer3 (you can't ping and there is no firewall) then you must move down the stack.

 

[PlatinumGold]

Originally posted by: spidey07
replace the cable with a known, working, good and tested cable.

You have a layer1 problem.

since the cables were working before he changed out his hub for the switch, i'd guess the problem is more likely to be with his switch. don't you think?

 

[OutHouse]

stand by for pics

 

[desertdweller]

If all of the machines are on the same subnet, the gateway isn't an issue. Verify the subnet masks are the same, such as 255.255.255.0

Check the ports on the hub and make sure you don't have one of the wires pluged into a port that says "Uplink" or "mdi/mdx". If you're not sure, then just don't use the first or the last port.

Try putting the machines into "Safe Mode with Networking" and see if they ping, if they do, then you have a program running blocking.

Make sure your network card is setup properly and enabled in the device manager.

DD

 

[mobobuff]

Go to a command prompt on each computer and type arp -a. Paste your results. So far I'm rather certain it's a problem with subnets and IP assignments.

 

[Kadarin]

Old Bay Networks switches? What's the config on that thing? Did you plug the cables into ports that are in different vlans?

 

[spidey07]

Originally posted by: PlatinumGold

Originally posted by: spidey07
replace the cable with a known, working, good and tested cable.

You have a layer1 problem.

since the cables were working before he changed out his hub for the switch, i'd guess the problem is more likely to be with his switch. don't you think?

Really I don't.

Some nics and some switches react differently to different out of spec cables. Some will auto-switch polarity (tip/ring), some will auto switch MDI/MDI-X interface. You just never know.

First - check your arp if you cannot ping. "arp -g"

If you do not have an arp entry for the destination host then layer2 isn't working. That leaves layer1 - the most common of all the most frustrating layers.

The most certainty for banging your head is using cables that you made yourself.

 

[JoLLyRoGer]

Originally posted by: Citrix

Originally posted by: JoLLyRoGer
1st rule of troubleshooting is to check your cables. Not trying to be Captain Obvious, but that includes the power cable to your hub. Have you tried pinging from one client machine to another to test out your hardware, or have you just tried pinging from your host (gateway) to your client boxes? Have you tried swapping in the old hardware (known good configuration), etc.

Seriously, don't overlook the small stuff.

Post back and LMK, Ok?

EDIT: Also, ask youself, "What changed between yesterday and today?" Start there..

Done all that. Changed out my NIC, Changed out the HUB, Tested my wires with a Fluke tester i borrowed from work. Have good lights on NIC's and on HUB. Nothing has changed. Can not ping any machine from any machine. they are blind except for when i unplug the wire and windows has that popup that says the network was disconnected.

OK, then it sounds like its time to start removing unknown quantities:

So far we know that it all worked yesterday...
We also know that cables and hardware is tested good...
From reading above it seems like you've verified your IP ranges and everthing IS running the same subnet (i.e. 199.199.199.xxx) and the same subnet mask (i.e. 255.255.255.0) Right?

And, you've verified that all computers are members of the same name-space (i.e. myworkgroup.home)

It doesn't really matter what your gateway IP is so long as it's in the same subnet where it can be discovered by the other clients.

Now, what we don't really know much about is this new switch. Swap in your old hub and then see if everything works again. If so we can definitively say it has something to do with the switch (thus removing an unknown quantity). If things are still jacked up with the known good hub then we have to look elsewhere.

LMK how it turns out..

JR..

 

[OutHouse]

Originally posted by: spidey07
replace the cable with a known, working, good and tested cable.

You have a layer1 problem.

-edit- link lights tell you nothing and do not mean the cable is good.

If you cannot operat at layer3 (you can't ping and there is no firewall) then you must move down the stack.

I tested my cabled with a tester and i just plugged my laptop into the network and still can not ping from my laptop.

 

[PlatinumGold]

Originally posted by: Citrix

Originally posted by: spidey07
replace the cable with a known, working, good and tested cable.

You have a layer1 problem.

-edit- link lights tell you nothing and do not mean the cable is good.

If you cannot operat at layer3 (you can't ping and there is no firewall) then you must move down the stack.

I tested my cabled with a tester and i just plugged my laptop into the network and still can not ping from my laptop.

again, why are you changing from hub to switch? i just don't see any advantage for a 2 or 3 node network.

 

[mobobuff]

Get to posting your arp -a results.

arp -g also does the same thing.

 

[spidey07]

Originally posted by: Citrix

Originally posted by: spidey07
replace the cable with a known, working, good and tested cable.

You have a layer1 problem.

-edit- link lights tell you nothing and do not mean the cable is good.

If you cannot operat at layer3 (you can't ping and there is no firewall) then you must move down the stack.

I tested my cabled with a tester and i just plugged my laptop into the network and still can not ping from my laptop.

Are these store bought patch cables or homemade?

If the latter then throw them out. You cannot depend on them.

If your IP address are correct (and they seem like they are) and you cannot ping your gateway then you know you have a layer1/2 problem.

check to see if you have a good arp for your gateway (no firewall involved in this as this is really layer 2/3)

If not then your cable/nic/hub is bad - a layer1 problem.

I remember bay 100 base-t hubs had a problem with autonegotiation. If it is truly a 100 Base-T hub then hard set the NIC to 100/half.

Also 100 Base-T hubs have a strict rule that no more than one can be used in a collision domain. Make sure there are no other hubs attached, although that is unlikely to cause you not to ARP/PING.

 

[Chrono]

good god. you can buy a damn router for 15-20 bucks at fry's (airlink). it's not the best but it WORKS.