Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SOHO3 Remote access issues - Remote Desktop

Status
Not open for further replies.

eddster

IS-IT--Management
Nov 11, 2002
28
GB
We've "Inherited" a client with a SOHO3 firewall.
We've put in a new server for the client running SBS 2003 which all works fine, internet access works fine etc and internally, we can test remote desktop access to the point of accepting the certificate and getting to the login in screen on the server.

Externally however, it won't work.

We have 3 rules in place, one to allow each of https(443), rdp(3389) and remote web(4125) which are the required ports. However, it's dropping the packets. I can see this in the log and it states that it was in accordance with rule 21. This is the default "Deny" rule.

Why the hell is it ignoring the other three previous rules telling it to allow traffic??

I have restarted the firewall, it made no difference.
I instated an explicit rule to allow access over https(443) from our external IP address. It still didn't work.

It looks like the firewall is ignoring all the other rules and just dropping the packets.

....and ideas anyone?

I know the ports are correct as this works for every other config we've done in the past. Just never met this one firewall before.

This is driving me crazy!!

Eddster....
 
Okay, an update.

Tried with a NetGear firewall and all worked fine.

I noticed something weird on the SonciWall logs.

For the three services (RDP, HTTPS, Remote Web), the lan server is 192.168.24.1 (this is the correct IP address, the gateway is set to 192.168.24.254). This is all correct.

The external IP we'll call x.x.x.5 for arguments sake.

When someone tries to connect with the web, the log shows the dropped https packets.

However, it shows them as follows:

Web Request, packet dropped
Source z.z.z.z (originating public IP address)
Destination x.x.x.5 (public IP address of firewall)

The destination should be 192.168.24.1
Why is it looping packets to the external interface and not passing them throught to the LAN server?

Is this something to do with the certificates? Do I have to somehow install the certificate on the firewall as opposed to having it orinigate from the server?

Any ideas would be appreciated, Ta!!!!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top