Being router-knowledge impaired, I need some assistance. Situation is this:
2 locations connected via 2 Cisco 2620 routers using Frame Relay. Location 1 using 10. private IP addressing, Location 2 using 192. private addressing. I have a server located in the 10. subnet which I would like to be able to access from the 192. subnet using a 192. IP address.
I tried adding a second IP address (192.168.10.46) to the single NIC in the server and also tried adding a second NIC with the 192. IP but could not get either option to work. Looking at the server's routing table (route print) the 192. route's Gateway and Interface default to the same IP (192.168.10.46) as the NIC's IP address. So 192. packets go nowhere. If I change the route for the 192. (route change) to point to the 10. Gateway IP address of the router on the 10. subnet, I can ping the 192. subnet from the 10. subnet but the 192. subnet cannot ping or tracert the 192.168.10.46 server IP address. I'm assuming this is because the 192. ping won't return to the 10. gateway??
Thanks for any help you can provide in solving this. Appreciate it if you can be somewhat descriptive in your ideas 'cause you know I'm router-knowledge impaired. Thanks
2 locations connected via 2 Cisco 2620 routers using Frame Relay. Location 1 using 10. private IP addressing, Location 2 using 192. private addressing. I have a server located in the 10. subnet which I would like to be able to access from the 192. subnet using a 192. IP address.
I tried adding a second IP address (192.168.10.46) to the single NIC in the server and also tried adding a second NIC with the 192. IP but could not get either option to work. Looking at the server's routing table (route print) the 192. route's Gateway and Interface default to the same IP (192.168.10.46) as the NIC's IP address. So 192. packets go nowhere. If I change the route for the 192. (route change) to point to the 10. Gateway IP address of the router on the 10. subnet, I can ping the 192. subnet from the 10. subnet but the 192. subnet cannot ping or tracert the 192.168.10.46 server IP address. I'm assuming this is because the 192. ping won't return to the 10. gateway??
Thanks for any help you can provide in solving this. Appreciate it if you can be somewhat descriptive in your ideas 'cause you know I'm router-knowledge impaired. Thanks