Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Setting up TFTP

Status
Not open for further replies.

TSupportEngineer

Technical User
Aug 2, 2005
53
US
Hi all. I have set up a 2500 series router to practice saving/loading images. The workstation IP is 192.168.1.10, the e0 is 192.168.1.11. The subnet mask is 255.255.255.0. The workstation is connected to the router to the e0 interface through a crossover cable and a tranceiver. The e0 interface is up/up. IP is running, as is RIP v1. I can't ping the workstation either with the crossover or a straight-through cat5 cable so I do not have a connection. I have Cisco's TFTP server on the workstation, but not being able to ping, I'm stuck (I can ping the e0 interface from the console and ping the workstation IP from the workstation). Any ideas? Thanks.
 
When you say each can ping itself, are you pinging the loopback address (127.0.0.1) on the workstation? This will verify that the IP stack is installed and okay on the workstation. Do you have a different workstation? Sounds like the NIC or the wonderful OS of NT Server 4.0 is causing you some problems. The two are directly connected, so you don't need a routing protocol, nor do you need to add a route. Did you do this via route add statements in a .bat file? Stop that!

Burt
 
I appreciate all the help. Let me answer one at a time.

1. I did ping the router from the workstation, then ran a sho arp. The output was only showing the e0 ip address.

2. Tried adding a route to the workstation again. Tried both the e0 interface as well as the NIC as gateways, no good. Still getting an error when trying to add routes. The routes were attempted to be added through a command prompt at the workstation. Doing a route print command does show the NIC ip on some of the routes.

3. Did an ipconfig and ipconfig/all. Pinged 127.0.0.1 successfully.

4. Changed the x-over cable, reinstalled the NIC to check for physical errors.

I am going to try to put a switch between the router and workstation and see if that helps. I hate these seemingly simple problems, but am too stubborn to stop. It's taking some time from my studying (re-cert in CCNA, and attempting the CCDA before July 1).

Again, I thank all of you for lending your grey matter. Have a good weekend. I'll post any new news.
 
You don't need any routes at all on the router or the workstation for this to work. Please remove all of them so they don't screw things up.

Regarding the ARP issue, did you not even see an Incomplete entry for the IP address of your workstation? If not then something else even more strange is wrong.

Please turn on "debug ip packet" and then try to ping the workstation again. Post the results.
 
I agree---these nodes are directly connected to eachother in the same subnet---route add commands in DOS can screw things up---the router routes, not the PC!!!

Burt
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top