Unable to view certain URLS in browser using Secure CRT

[vanbaster]

I am a new user and having the following problem.

Current setup:

Without Putty connection to bastion server:
Company URL - Cannot Access

With putty connection to Bastion server
Putty > connect to bastion server > connect to linux Great!
Putty > connect to bastion server > company url on browser > Great! page loaded

With SecureCRT connected to Bastion Server:
SecureCRT > connect to bastion server > connect to linux Great!
SecureCRT > connect to bastion server > company url on browser > cannot connect!


It looks like the browser is not recognizing that I am connected to the bastion server when using SecureCRT.

Thanks!

[jdev]

Hello "vanbaster",

SSH clients like SecureCRT and putty don't typically provide URL forwarding without some type of port forwarding (AKA tunneling) configuration being enabled in the SSH client.

• What port forwarding configuration have you set up in putty?
• How does this compare with SecureCRT's port forwarding configuration?
• If you enable Trace Options in SecureCRT's File menu prior to connecting to the session in SecureCRT, what gets revealed in SecureCRT's terminal window after you attempt to connect to the company URL in your browser once you're successfully connected with SecureCRT?
  

  Note: Trace Options output may contain sensitive data that you may not want displayed to the world in a public forum such as this. If you need help deciphering the trace options output, please send your trace options debug log by email to support@vandyke.com with a Subject referencing: Forum thread 14172.

My guess is that your trace options logging may reveal that your port forward filters in SecureCRT are preventing the web client from connecting because its source IP is not the local loopback adapter of your machine. SecureCRT allows only loopback adapter sources to connect to forwarded ports by default.

If you do end up needing to adjust your port forward filters, the process is described in the "How do I modify port-forwarding filters in SecureCRT?" section of our SecureCRT FAQ.

Effectively, if you want to allow anyone who has network access to your machine to connect from any source IP address, you'd modify your session .ini file so that the line...

S:"Port Forward Filter"=allow,127.0.0.0/255.0.0.0,0 deny,0.0.0.0/0.0.0.0,0

...reads instead as:

S:"Port Forward Filter"=allow,0.0.0.0/0.0.0.0,0

Remember to close all instances of SecureCRT that are running before you make any changes to the underlying .ini file.

--Jake

[vanbaster]

Hello Jdev,

What port forwarding configuration have you set up in putty?
How does this compare with SecureCRT's port forwarding configuration

Local Portforwarding on both is identical

If you enable Trace Options in SecureCRT's File menu prior to connecting to the session in SecureCRT, what gets revealed in SecureCRT's terminal window after you attempt to connect to the company URL in your browser once you're successfully connected with SecureCRT?

Nothing shows up in the terminal window. Only no internet on browser window

[jdev]

Originally Posted by vanbaster

Local Portforwarding on both is identical

Which version of SecureCRT are you running?

On which operating system do you have SecureCRT installed and running?

I take it that port forwarding is enabled in both SecureCRT and putty?

Please provide screen shots showing the identical nature of the port forwarding configuration in putty vs. SecureCRT (again, use email if public forum posting is undesired).

If you enable Trace Options in SecureCRT's File menu prior to connecting to the session in SecureCRT, what gets revealed in SecureCRT's terminal window after you attempt to connect to the company URL in your browser once you're successfully connected with SecureCRT?

Originally Posted by vanbaster

Nothing shows up in the terminal window. Only no internet on browser window

If nothing shows up in SecureCRT's terminal window after a) you've connected with SecureCRT to the remote SSH2 server and b) you've tried to connect to your URL using your browser, then the only logical conclusion that seems to exist is your web browser isn't connecting to the same local port that you have SecureCRT configured to forward.

Please provide details of your configuration and setup (again, use email if public forum posting isn't desired).

--Jake

[vanbaster]

Email sent.

[jdev]

This issue is resolved.

The problem was that the import into SecureCRT from putty was done using a script that does not yet support pulling in port forward configurations that are dynamic forwards -- only local port forward entries are pulled in.

An explicit dynamic port forward entry needed to be added manually after the import.

--Jake