First of all, I live in an apartment complex with an intranet setup. Network setup: Internet | Apartment Intranet(10.x.x.x) | My network(192.x.x.x) / \ Computer1 Server 2003 The reason I set up my own network is because the complex's network is strictly wireless. I didn't like that setup so I set up my own wireless network off a router wired into their network so that I could have nearly complete control over the network I was on. Since we are on a dynamic IP I set up a DynDNS account. Now, my question: I am trying to set up a Server 2003 machine with remote access through Remote Desktop. I can connect from my Win7 machine to the server through RD using the local address of the server. But, whenever I try to connect through the DynDNS connection it times out. I can ping the DynDNS connection. Port 3389 can't be seen from outside the network. Is this problem because of their network being inline with mine? Am I to assume that they don't have a wide-open gateway?

" I can connect from my Win7 machine to the server through RD using the local address of the server" From what location? Yes likely port 3389 is not being forwarded. You can test here. http://www.canyouseeme.org/ Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows]

Hi, Thank you for your post here. Do you have the wireless router as the gateway for your network? Do you have NAT enabled on this router? If you enable NAT on both routers, you will need to configure port forwarding on both router to publish RDP 3389 to internet. Otherwise, you should disable NAT on the router which acts as the gateway for your network.