Howday folks,
We use a bunch of external systems that identify us by our IP range.
We also have a lot of users that need to access these systems from out with our network and as such are required to log in.
We have MANY systems that work like this and due to this high number we inevitably sometimes have access problems reported by our users from outside the network.
To debug these problems we use a secondary line (that is used for other purposes as well) which we attach a laptop to and thus are outside out network.
It occurs to me that this is archaic and we should be able to streamline this process.
I'm aware of proxy clients that can be used free of charge that can give you an alternative IP address but we obviously want to keep everything above board.
I've suggested simply setting up TOR on our PC's with a plugin that would allow us to enable and disable external access as required but when management read about this they are more worried about the risks of "anonymous browsing".
Any suggestions?
We use a bunch of external systems that identify us by our IP range.
We also have a lot of users that need to access these systems from out with our network and as such are required to log in.
We have MANY systems that work like this and due to this high number we inevitably sometimes have access problems reported by our users from outside the network.
To debug these problems we use a secondary line (that is used for other purposes as well) which we attach a laptop to and thus are outside out network.
It occurs to me that this is archaic and we should be able to streamline this process.
I'm aware of proxy clients that can be used free of charge that can give you an alternative IP address but we obviously want to keep everything above board.
I've suggested simply setting up TOR on our PC's with a plugin that would allow us to enable and disable external access as required but when management read about this they are more worried about the risks of "anonymous browsing".
Any suggestions?
