Good job!! though I think some of the confusion was the question of pinging "from" hyperterm. Your only connecting to another device from hypertem and it is from this device, a router, Cork in this case, from which you are pinging.
Dave Greg Macaulay wrote: > > Stop the presses -- > > I solved the problem!!!! > > (1) I needed to have connectivity between the router and my LAN. So I > connected the E0 interface to the Cable-Modem Router (10/100). > (2) Then I configured the E0 interface to be on the same subnet as my LAN. > > And much to my "aged" amazement (and relief!) -- it worked. > > BTW -- one can ping in hyperterminal -- from the router to the PCs on the > LAN. > > Cork>ping 192.168.1.101 > Type escape sequence to abort. > Sending 5, 100-byte ICMP Echos to 192.168.1.101, timeout is 2 seconds: > !!!!! > Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms > Cork>ping 192.168.1.103 > Type escape sequence to abort. > Sending 5, 100-byte ICMP Echos to 192.168.1.103, timeout is 2 seconds: > !!!!! > Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms > Cork> > > Lastly, thanks for your offers of assistance. I do feel a bit stupid in > bothering everyone. But it's been a few months since I fired up these > routers and I overlooked some basics!! Oh well . . . . > > Thanks again -- and I owe you one. > > Greg Macaulay > Oldest Human Being preparing for the CCIE Lab > Lifetime AARP member > Retired Attorney/Law Professor > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:nobody@;groupstudy.com] > > Sent: Thursday, October 31, 2002 10:00 PM > > To: [EMAIL PROTECTED] > > Subject: RE: Problems w/Hyperterminal?? [7:56619] > > > > > > Creighton Bill-BCREIGH1 wrote: > > > > > > > > How can you ping from a DOS prompt if the destination is > > > crossing a repeater > > > with a speed mismatch? A FastEthernet-only hub won't allow > > > comms between > > > 10Mb/s devices, so if you wouldn't have any visibility to that > > > device, > > > whether from a DOS prompt, Hyperterminal, or anything... > > > > > Good point. If a station can send a packet, such as a ping, it's unlikely > > that there are any physical or data-link-layer problems. If it > > can't receive > > a packet, it makes sense to look above those layers. There are some > > unidirectional problems, but they are pretty rare. Some > > protocols, including > > STP, deal with the infamous "one-way connectivity" problem, but I bet it > > happens pretty rarely. > > > > I had a new theory about what would cause his symptoms, or at least what I > > think his symptoms are: > > > > PC can ping router. > > PC can Telnet to router?? (we're not sure if he's Telnetting or not) > > Router can't ping PC. > > Router can't TFTP a file to the PC. > > > > Possible explanation: the PC is running a firewall! From my > > knowledge of the > > default behavior of many personal firewalls, this seems rather likely. > > > > There could be an access list on the router too that could cause this. > > > > Gotta run. I promise no more messages on this topic! ;-) > > > > _______________________________ > > > > Priscilla Oppenheimer > > www.troubleshootingnetworks.com > > www.priscilla.com -- David Madland CCIE# 2016 Sr. Network Engineer Qwest Communications 612-664-3367 "You don't make the poor richer by making the rich poorer." --Winston Churchill Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=56720&t=56619 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
