Shoutbox

DNS help - Printable Version

-Shoutbox (https://shoutbox.menthix.net)
+-- Forum: MsgHelp Archive (/forumdisplay.php?fid=58)
+--- Forum: Skype & Technology (/forumdisplay.php?fid=9)
+---- Forum: Tech Talk (/forumdisplay.php?fid=17)
+----- Thread: DNS help (/showthread.php?tid=53347)

DNS help by Wabz on 11-26-2005 at 08:29 PM

Hey guys,

My new ISP gave me a static address :D

I set up a subdomain to point to this address  say for this example 192.168.1.1

Now at home we have a 5 port router managing the internet connection.

Behind this router we have a server in the DMZ  sat on internal host 10.0.0.254

Any ideas how I get the the host  to bind to this machine so I can remote desktop to it from an external location?


RE: DNS help by Menthix on 11-26-2005 at 08:54 PM

Just point the domain to your external internet IP. The server is on DMZ, so traffic will end up there.


RE: DNS help by Wabz on 11-26-2005 at 10:45 PM

Cool It resolves and pings :)

But I can't connect to the box at all.  Remote Desktop Connection fails


RE: DNS help by Menthix on 11-26-2005 at 10:48 PM

Maybe the router firewall, or firewall on the server, is blocking it?


RE: DNS help by Underlord on 11-26-2005 at 11:27 PM

If it's DMZ then the router shouldn't be blocking it. Does remote desktop work internally? You might want to try manually forwarding TCP port 3389 and see if that works. Also make sure the default gateway on your DMZed box is pointed to the router.


RE: DNS help by Menthix on 11-26-2005 at 11:46 PM

quote:
Originally posted by Underlord
If it's DMZ then the router shouldn't be blocking it.
I know my router does, so i can imagine there are mre that do it.

Mine goes like...
- Check if traffic is allowed by firewall, proceed if it is.
- Check if there is a NAT rule for the traffic, forward traffic if there is, proceed it there isn't
- Send traffic to DMZ.
RE: DNS help by rav0 on 11-27-2005 at 02:41 AM

quote:
Originally posted by Wabz
Any ideas how I get the the host  to bind to this machine so I can remote desktop to it from an external location?
Remote Desktop Connection is a part of Windows (duh). I don't know how to get Windows to bind to an IP address that you specify just for Remote Desktop Connection, and not mess up the NAT.

As far as I can tell the reason you can use Remote Desktop Connection from WAN is that Windows is being confused by the NAT and doesn't understand which IP address it actually has.
RE: DNS help by Wabz on 11-27-2005 at 11:54 AM

quote:
Originally posted by rav0
Remote Desktop Connection is a part of Windows (duh). I don't know how to get Windows to bind to an IP address that you specify just for Remote Desktop Connection, and not mess up the NAT.

As far as I can tell the reason you can use Remote Desktop Connection from WAN is that Windows is being confused by the NAT and doesn't understand which IP address it actually has.

You can override NAT with port forwarding :P .  Basically its a statement that says anything inbound on this port send here
RE: DNS help by ShawnZ on 11-27-2005 at 01:05 PM

quote:
Originally posted by Wabz
You can override NAT with port forwarding

No you can't?

quote:
Originally posted by rav0
Windows is being confused by the NAT and doesn't understand which IP address it actually has.

Windows XP would do the "Limited or no connectivity" thing in that case.
RE: DNS help by Concord Dawn on 11-27-2005 at 02:47 PM

You don't even need to DMZ it. Just set up a port forward for whatever the Remote Desktop port is.

Personally, I'd get UltraVNC and run a VNC server on it. I don't like RDP in the slightest.

BTW, I'm assuming that you're running Windows


RE: RE: DNS help by rav0 on 11-28-2005 at 04:28 AM

quote:
Originally posted by Wabz
You can override NAT with port forwarding :P .  Basically its a statement that says anything inbound on this port send here
I know what NAT is. When using using port forwarding, DMZ, or none of these in a NAT environment, the remote computer knows that it is communicating with the WAN IP address, but the local computer knows that it has a LAN IP address. This is where I suggested that the problem might be occuring.