My company uses a VPN to allow outside access to our inhouse systems.
Our main software here runs on a Unix server, so an emulation program has to be used on Windows systems. We use Tiny Term for this.
We have one employee who lives out of state and does all of her work through this VPN connection. She has recently moved and went from a Bellsouth DSL connection to a Sprint DSL connection and she's now having problems connecting with the emulator. There is no problem connecting to the VPN, but the emulator will not connect to the inhouse server.
This sounds like a routing problem on her end. Most likely NAT settings on her modem/router that are not allowing the connection to complete, but that seems strange since the VPN has no trouble connecting. It seems that the emulator connection would use the same ports as the VPN correct?
I may not be explaining this the best way, but bear with me. What could cause the emulator connection to time out like this? Am I right in thinking its a router configuration issue?
Our main software here runs on a Unix server, so an emulation program has to be used on Windows systems. We use Tiny Term for this.
We have one employee who lives out of state and does all of her work through this VPN connection. She has recently moved and went from a Bellsouth DSL connection to a Sprint DSL connection and she's now having problems connecting with the emulator. There is no problem connecting to the VPN, but the emulator will not connect to the inhouse server.
This sounds like a routing problem on her end. Most likely NAT settings on her modem/router that are not allowing the connection to complete, but that seems strange since the VPN has no trouble connecting. It seems that the emulator connection would use the same ports as the VPN correct?
I may not be explaining this the best way, but bear with me. What could cause the emulator connection to time out like this? Am I right in thinking its a router configuration issue?