|
Home > Archive > CCNA > September 2000 > need help
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| Have set up the following network and can not get onethe ws on the same hub to ping
Lab a s0 172.16.1.1 sm 255.255.255.128
Lab b so 172.16.1.2 and the e0 is 172.16.2.1
both ws are connected to lab b hub with addresses of 172.16.2.2 and 172.16.2.3
I can can ping from dos to all ports fron the 172.16.2.2 BUT I can not ping from the 172.16.2.3 any where I have the gateway set on both to 172.16.2.1 255.255.255.128 what
am I doing wrong. | |
|
| I'll take a shot until somebody who knows what they are doing comes along - your wording is a little unclear for starters
1. what is the output of the command 'sh ip route' from each router, do you see any routes?
2. have you enabled rip? or are you using static routes
3. have you brought up each interface with the 'no shut' command, if you have not they will show up as 'administratively down' in the 'sh interface' output, hope some of my mud sticks!
as to the ip addresses you have I am a little unclear, is this a real router you are using or a sim?
[This message has been edited by LeX (edited 09-23-2000).] | |
|
| on the surface there is nothing wrong with your addressing. 172.16.2.1, 172.16.2.2, & 172.16.2.3 w/ mask of 255.255.255.128 all fall into the same subnet(172.16.2.0/25) the default gateway is irrelevant if 172.16.2.3 can't even reach it's subnet peers on the same hub. So your problem is something else. Verify you have a link light. Try a different hub port. try a different cable. double check your configuration. if possible, you could also try a crossover cable between ws 1 & 2 with the same addressing to rule out problems with the hub. Although that's doubtful the problem, it's always a possibility.
| |
|
| i took a second look at your wording. It's really vague. when you say you can't ping anywhere, i took it to mean you can't even ping your subnet peers on the same local hub. If this isn't the case, be more specific on which interfaces and ws's you can or can't ping from that workstation
| |
|
| quote:
Originally posted by Detour:
i took a second look at your wording. It's really vague. when you say you can't ping anywhere, i took it to mean you can't even ping your subnet peers on the same local hub. If this isn't the case, be more specific on which interfaces and ws's you can or can't ping from that workstation
From ws 172.16.2.3 can not ping 172.16.2.1 172.16.1.2 or 172.16.1.1 I have checked all of the cable and hubs from the 172.16.2.2 i am not having any problems both ws are conected to the hub connected to router b
| |
|
| quote:
Originally posted by LeX:
I'll take a shot until somebody who knows what they are doing comes along - your wording is a little unclear for starters
1. what is the output of the command 'sh ip route' from each router, do you see any routes?
2. have you enabled rip? or are you using static routes
3. have you brought up each interface with the 'no shut' command, if you have not they will show up as 'administratively down' in the 'sh interface' output, hope some of my mud sticks!
as to the ip addresses you have I am a little unclear, is this a real router you are using or a sim?
[This message has been edited by LeX (edited 09-23-2000).]
The ip routes shows all of the connections are correct between the interfaces.
i have 2 routers and a hub set up with the hub connected to router b and router b is connected to router a
| |
|
| quote:
Originally posted by Detour:
i took a second look at your wording. It's really vague. when you say you can't ping anywhere, i took it to mean you can't even ping your subnet peers on the same local hub. If this isn't the case, be more specific on which interfaces and ws's you can or can't ping from that workstation
ws 1 and 2 are connected to a hub which is connected to router b and router b is connected to router a
from ws 2 I can not ping any port on router b or router a. the other ws which is connected to the same hub I can ping to all ports on both routers.
| |
|
| The problem:
Workstation(172.16.2.2) can ping the routers,
but WS(172.16.2.3) cannot. You did not
specify but I believed the WS cannot ping
each other.
The others have given you some good advices
of where to look. I am not an expert by any
mean but try this:
1. Swap the patch cables of the WS(s)
and try pinging again.
2. Ping 127.0.0.1 is a loopback test. It's
quick test on the NIC card, but not a
through test.
3. At the C:\>, enter "ipconfig" for NT,
or "winicfg" for Win95. It should show
the settings for the NIC card you'd
entered. Sometimes the setting won't change till the computer is rebooted.
Sounds like the problem is isolated to that
one WS. Hope this help.
| |
|
| quote:
Originally posted by hwl130:
The problem:
Workstation(172.16.2.2) can ping the routers,
but WS(172.16.2.3) cannot. You did not
specify but I believed the WS cannot ping
each other.
The others have given you some good advices
of where to look. I am not an expert by any
mean but try this:
1. Swap the patch cables of the WS(s)
and try pinging again.
2. Ping 127.0.0.1 is a loopback test. It's
quick test on the NIC card, but not a
through test.
3. At the C:\>, enter "ipconfig" for NT,
or "winicfg" for Win95. It should show
the settings for the NIC card you'd
entered. Sometimes the setting won't change till the computer is rebooted.
Sounds like the problem is isolated to that
one WS. Hope this help.
I tried the 127.0.0.1 and it worked the two WS will not ping eacher other. The cables checked out and the nic on the 172.16.2.3 is working any other sugestions
| |
|
| I am assuming this computer is in a domain. Are these static IP's or are you using DHCP.
If they are DHCP check the subnet mask. I came across a somewhat similar problem where for some reason DHCP was assinging the wrong subnet mask to one individual computer. in order to resolve it I uninstalled TCP/IP and reinstalled, and also removed and added the computer back to the domain. Of course if you remove a computer from the domain wait 15 minutes to re-add, So it can properly be removed from all browsing lists.
Another thing to check is your WINS settings. You can add static WINS addresses. check if your getting one with DHCP if you are. Find out if your network has a second WINS server and add that staticly.
WHo knows...... | |
|
| he didnt say anything about a server as well as the workstation so I doubt either ws is in a domain. WINS is irrelevant here, unless for some odd reason he's only pinging netbios names and not ip addresses. And even then, the netbios type would have to be P, else it will broadcast for the name if it couldnt get to the WINS server. it sounds like he's running static ip's
from what i gather, he has two routers and two workstations. the two workstations and one router are patched into a hub. ok let's go top down on this.
ws 2 cannot ping anybody including workstation 1 or router's ethernet interface, so we can rule out any router problems. if he's switched the cables between the workstation and still the same problem, I'd suggest he try a different port on the hub for WS 2 too. if it still doesn't work, we can for the most part rule out problems with the hub or cable.
so that leaves us the workstation itself. We'll assume he has the right nic drivers for his card, and his configuration is ok. he didn't say if this is 95 or NT. either way, my suggestion is to wipe the network settings, and reinstall the nic card driver/protocols. on 95, delete the adapter, reboot, it'll plug and play, reinstall the drivers.
anyways, you are able to ping the loopback, but I've seen where you can do this when the card is faulty, or when you have the wrong nic driver. if it still doesnt work after a reinstall, it's most likely a faulty nic card. try swapping the nics in 1 & 2 or put a new one in 2
| |
|
| The reason for checking the WINS settings was to see if he could ping computer names. Forgot to add that... | |
|
| quote:
Originally posted by beenframed:
The reason for checking the WINS settings was to see if he could ping computer names. Forgot to add that...
I have checked all cables and the winipcfg.exe and it shows the ip addrss and mac address/ The settings show the nic is working properly. I still can not ping
Could the nic card still be bad even if it is showing that it is working.
|
|
|
|
|