Link to home
Start Free TrialLog in
Avatar of Ethan Darwin
Ethan Darwin

asked on

Route source to destination

I have a customer with an old phone system that uses a VPN between sites.

The phone system incorrectly uses the server IP 192.168.1.50 as the GW and hence cannot connect. The correct GW is 192.168.1.254

Unfortunately the phone's IP settings are not dynamic and nobody knows the password to change the settings.

As the phone is looking to 192.168.1.50 for a gateway instead of 192.168.1.254 is it possible to route all traffic from the phone's IP 192.168.1.10 to 192.168.1.254.

The server is a Windows2003 server.

As the phone only connects with via the VPN there all it's traffic is bound for the VPN.
Avatar of MarcusSjogren
MarcusSjogren

Since it seems to be a funky situation already - can't you just add 192.168.1.50 as a secondary IP address on the gateway (192.168.1.254)?
It will be the most logical and easy solution.

Edit: Most logical solution would ofc be to reset the telephones, but I you know... situation is what it is :-)
Avatar of Ethan Darwin

ASKER

Hi Marcus, thanks for the suggestion, I had thought of this  however the ip 192.168.1.50 is already in use on the server.
ASKER CERTIFIED SOLUTION
Avatar of hypercube
hypercube
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
and the extra router solution above seems at first of all impossble, because you just don't route some parts of a subnet differently, it's a bad idea.
Secondly you would still have to remove the IP from the server, so you might as well just add it to your current router.

sorry, but it's the only suitable solution if you cannot re-configure the phones.

If it is very important to reach the server via .50, you can also setup NAT for the interesting ports and forward them to the server.
Thanks for the excellent feedback and suggestions. I think the simplest solution is to assign 192.168.1.50 to the router and reconfig the LAN to reflect the new router IP.

Once face value I think it should be a relatively straight forward process however experience has taught me there is no such thing...
p.s. They found the password :)
Normally the router can have both .50 and .254 address so it would require minimum effort :-)

Haha, good to hear. Good luck!