Calling all Firewall NG gurus
Well, after the dell problem, I have yet another problem related to firewalls. We managed to get the firewall running with a few minor problems (lost arps under w2k anyone).
So its all up and running. However, when I try to use securemote I keep being told that the communication failed even though I logged on with the correct password and username. It logs me on but then disconnects.
However if I do this with a nildram dialup connection, it works fine with no problems. Anyone encountered this before ? Any ideas ?
Much appreciated if anyone can help me fix it.
So its all up and running. However, when I try to use securemote I keep being told that the communication failed even though I logged on with the correct password and username. It logs me on but then disconnects.
However if I do this with a nildram dialup connection, it works fine with no problems. Anyone encountered this before ? Any ideas ?
Much appreciated if anyone can help me fix it.
Now there you have me as I havent got access directly to the firewall from the adsl connection because the s/w is at work. I will look first thing tommorow and post it. Thanks for the help btw
You mention ADSL ?
Are you on a shared ADSL connection ? (ADSL "router") or a single machine on the ADSL.
If you are using NAT on the router, you need to "tweak" your firewall to allow for securemote and NAT.
J.
Are you on a shared ADSL connection ? (ADSL "router") or a single machine on the ADSL.
If you are using NAT on the router, you need to "tweak" your firewall to allow for securemote and NAT.
J.
My secureremote client shows on the CP-FW1/VPN1 link as it's internal 192.168.n.n address.
This caused a few scratches of heads initially as the company internals are 10.n.n.n addresses ........
Steve
This caused a few scratches of heads initially as the company internals are 10.n.n.n addresses ........
Steve
Trending Topics
We recently enabled VPN on our FW1 NG install on a Dell servers.
What a major pain that was. Ended up using network packet sniffers to see why the VPN wasn't working. To cut a long story short, we solved it by using the first network interface that Win2k enumerates as the external interface.
We use a PE2450. Onboard NIC has now become the external interface.
HTH
H
What a major pain that was. Ended up using network packet sniffers to see why the VPN wasn't working. To cut a long story short, we solved it by using the first network interface that Win2k enumerates as the external interface.
We use a PE2450. Onboard NIC has now become the external interface.
HTH
H
Thread
Thread Starter
Forum
Replies
Last Post
Mattybr5@MB Developments
Full Cars Breaking For Spares
12
Nov 18, 2015 07:03 AM



