Remote Desktop Problems - Please Help
Dec 07 05 11:51 pm
Hi,
My first post.
I am trying to use remote desktop from the internet to a pc (not WG PC) on our network.
WHAT I HAVE:
1 - Router with a dynamic internet address - I use No-IP for resolution
2 - Router has static Lan address - 72 (these are just the last 2 numbers - first numbers are all the same on the LAN)
3 - The router has port 3389 open in its firewall and I set the virtual server settings to port forward 3389 to the 73 Nic in the Wingate PC.
4 - Wingate PC has 2 network cards. 73 to router and 70 to switch (rest of lan)
5 - All other computers on the lan are 51 to 69.
WHAT I CAN DO:
1 - I can control the Wingate PC from the internet - (if i turn on remote desktop on the WG PC) - This tells me the router/modem(DSL) has the correct firwall ports open and it is forwarding it to 73.
2 - In port security I can use redirect (lan to WG PC) Port 3389 to redirect one pc to another. THIS WORKS. Ie If 51 connects to 70 (wingate pc) it redirects to 56 (another PC on lan).
3 - All other features are working - ie ww proxy and some mapping for gmail etc.
WHAT I NEED TO DO BUT CANNOT!
1 - I set up wingate to allow port 3389 and forward it to IP 56. TCP Connections from the internet.
2 - If i try to connect from the internet (RD is turned off on the Wingate PC) then I get a message that it could not connect. The system tray icon flashes when i connect but NOTHING appears in wingates activity window.
Any help would be appreciated.
Thanks
Simon.
My first post.
I am trying to use remote desktop from the internet to a pc (not WG PC) on our network.
WHAT I HAVE:
1 - Router with a dynamic internet address - I use No-IP for resolution
2 - Router has static Lan address - 72 (these are just the last 2 numbers - first numbers are all the same on the LAN)
3 - The router has port 3389 open in its firewall and I set the virtual server settings to port forward 3389 to the 73 Nic in the Wingate PC.
4 - Wingate PC has 2 network cards. 73 to router and 70 to switch (rest of lan)
5 - All other computers on the lan are 51 to 69.
WHAT I CAN DO:
1 - I can control the Wingate PC from the internet - (if i turn on remote desktop on the WG PC) - This tells me the router/modem(DSL) has the correct firwall ports open and it is forwarding it to 73.
2 - In port security I can use redirect (lan to WG PC) Port 3389 to redirect one pc to another. THIS WORKS. Ie If 51 connects to 70 (wingate pc) it redirects to 56 (another PC on lan).
3 - All other features are working - ie ww proxy and some mapping for gmail etc.
WHAT I NEED TO DO BUT CANNOT!
1 - I set up wingate to allow port 3389 and forward it to IP 56. TCP Connections from the internet.
2 - If i try to connect from the internet (RD is turned off on the Wingate PC) then I get a message that it could not connect. The system tray icon flashes when i connect but NOTHING appears in wingates activity window.
Any help would be appreciated.
Thanks
Simon.
Dec 08 05 12:04 am
Can you connect to this 56 machine from Wingate machine?
Dec 08 05 8:47 am
I have a client that pretty much has same setup and does what you want to do. Here is a screenshot of how I setup the port redirection (WG 6.1)
To remote in the user adds :3397 (non standard port) to the IP in the remote desktop connection screen as we have more than one LAN machine setup for remote desktop. The only time I have seen your issue is when the IP address of the router changes and an old IP is entered. So, are you sure that the name is being resolved to the right IP? Try it by direct IP entry.
To remote in the user adds :3397 (non standard port) to the IP in the remote desktop connection screen as we have more than one LAN machine setup for remote desktop. The only time I have seen your issue is when the IP address of the router changes and an old IP is entered. So, are you sure that the name is being resolved to the right IP? Try it by direct IP entry.
Dec 08 05 8:36 pm
Hi,
So i read genie's post and thought 'well of course i can'. Turns out I couldn't.
Always the simple things.
Anyway I changed the IP address of the Nic connected to the INET router to another totally different address - and changed the router to match.
Now it works 100%.
It appears windows gets confused if 2 NIC's in the same machine are on the same network.
Thanks for the help.
Later
Simon.
So i read genie's post and thought 'well of course i can'. Turns out I couldn't.
Always the simple things.
Anyway I changed the IP address of the Nic connected to the INET router to another totally different address - and changed the router to match.
Now it works 100%.
It appears windows gets confused if 2 NIC's in the same machine are on the same network.
Thanks for the help.
Later
Simon.
Dec 08 05 9:19 pm
Aye, this kind of setup is quite difficult for the systems to follow. Glad it works now, though.