Engineer
Elite Member
Bear with me as I'm not a networking guy so if I ask something "goofy", let me know.
My company has installed an automation project that we need to access at a clients facility. Currently, we have a VPN to our installed server on network card #1. As far as I know, the server has a 2nd network card that is on network #2. Is there a way that we can go through the customer's Citrix VPN (which allows access on the server network #1) and pass though to the network #2?
ME <-------VPN---------> [network 1: Server : Network 2] <---??-----> stuff?
Network 1 is in the 10.24.1.16x range
Network 2 is in the 192.168.220.xxx range
Possible to use the ROUTE command or something similar on the server (or on in combination with my work PC) to accomplish me being able to access the 192.168.220.xxx IP range through the VPN?
I know that the best solution would be to place the 192.168.220.xxx range on it's own VPN but the customer doesn't want to do that (don't know why). Any idea's or suggestions would be appreciated.
Remember...I'm not a networking guy, lol...so don't throw too much terminology at me! 😛
My company has installed an automation project that we need to access at a clients facility. Currently, we have a VPN to our installed server on network card #1. As far as I know, the server has a 2nd network card that is on network #2. Is there a way that we can go through the customer's Citrix VPN (which allows access on the server network #1) and pass though to the network #2?
ME <-------VPN---------> [network 1: Server : Network 2] <---??-----> stuff?
Network 1 is in the 10.24.1.16x range
Network 2 is in the 192.168.220.xxx range
Possible to use the ROUTE command or something similar on the server (or on in combination with my work PC) to accomplish me being able to access the 192.168.220.xxx IP range through the VPN?
I know that the best solution would be to place the 192.168.220.xxx range on it's own VPN but the customer doesn't want to do that (don't know why). Any idea's or suggestions would be appreciated.
Remember...I'm not a networking guy, lol...so don't throw too much terminology at me! 😛