I have WinGate installed on a Windows 2003 Server with a hardware firewall for the Internet. The hardware firewall has port forwarding to allow me to remote Desktop into the WG server and another TS server. The other TS server is set to use Port 3390 for RDP.
Since I have installed Wingate I cannot remote into the TS server anymore. No matter how I configure Extended Networking, Port Security, it never connects. I can connect to the WG server no problem.
The TS server is using the WG server as its Gateway so routing should not be a problem.
Does anyone have an idea what is going on here?
Is there any way I can stop WG from interfeering with port 3390?
Remote Desktop
Moderator: Qbik Staff
4 posts
• Page 1 of 1
Re: Remote Desktop
by Nev » Apr 07 08 9:57 pm
Hi Tony,
At a few locations I have your configuration and what I do is to create a redirect in Wingate's NAT.
It looks something like this:
Once the traffic is allowed through your hardware firewall Wingate will redirect it to the IP and Port of the other TS.
At a few locations I have your configuration and what I do is to create a redirect in Wingate's NAT.
It looks something like this:
Once the traffic is allowed through your hardware firewall Wingate will redirect it to the IP and Port of the other TS.
--
Nev.
Nev.
- Nev
- WinGate Guru
- Posts: 861
- Joined: Sep 22 03 11:35 pm
- Location: Mudgee ~ NSW ~ Australia
by tonysteele » Apr 08 08 10:26 am
Thanks Nev,
I like to control RDP connections by limiting the IP address they can come from. This is done in the Hardware firewall.
I suspect this is the problem where I am port forwarding from the Hardware firewall then trying to port forward in Wingate as well. I don't think it can route back to the external address.
I need Wingate to ignore all traffic on port 3390 not just allow it through. If I shutdown Wingate I can instantly RDP to the second machine.
I think I have just fixed it. While testing I only have one network adaptor on the WG machine. In Port Security I have allowed port 3390 in "Connections from the Internet", LAN connections to WinGate PC, and everything going to the WG PC. Seems ok so far.
PS. I just rebooted the WG PC and RDP to the second PC is failing again.
I like to control RDP connections by limiting the IP address they can come from. This is done in the Hardware firewall.
I suspect this is the problem where I am port forwarding from the Hardware firewall then trying to port forward in Wingate as well. I don't think it can route back to the external address.
I need Wingate to ignore all traffic on port 3390 not just allow it through. If I shutdown Wingate I can instantly RDP to the second machine.
I think I have just fixed it. While testing I only have one network adaptor on the WG machine. In Port Security I have allowed port 3390 in "Connections from the Internet", LAN connections to WinGate PC, and everything going to the WG PC. Seems ok so far.
PS. I just rebooted the WG PC and RDP to the second PC is failing again.
- tonysteele
- Posts: 2
- Joined: Apr 07 08 7:28 pm
by Nev » Apr 08 08 4:45 pm
Ok Tony,
A second NIC as an 'Internal' one is the usual method for Wingate to operate with.
If you have source routing in the external firewall it should be fairly secure and with the opening of the port to Wingate --> then a Port Forward should put your session into the second TS Server.
Just make sure the 'Internal' NIC in Wingate has only an IP and Mask, no DNS or Gateway.
A second NIC as an 'Internal' one is the usual method for Wingate to operate with.
If you have source routing in the external firewall it should be fairly secure and with the opening of the port to Wingate --> then a Port Forward should put your session into the second TS Server.
Just make sure the 'Internal' NIC in Wingate has only an IP and Mask, no DNS or Gateway.
--
Nev.
Nev.
- Nev
- WinGate Guru
- Posts: 861
- Joined: Sep 22 03 11:35 pm
- Location: Mudgee ~ NSW ~ Australia
4 posts
• Page 1 of 1
Who is online
Users browsing this forum: Google [Bot] and 20 guests