Nuvox T1 and RDP
Hi,
I am having difficulty successfully setting up RDP connections to an office with a fractional T1 voice/data line provided by Nuvox Communications. The RDP host is funtional, as it can be accessed across the LAN, but not from outside. I am familiar with the router port forwarding requirements as I have about half a dozen computers on different networks which I set up and use via RDP. On several of them RDP utilizes a non-standard port other than 3389.
This is the only network which uses Nuvox for data/voice communications with the outside world, and I think this is where I am going wrong. The information I am getting from Nuvox regarding public static IP addresses is suspect, as it varies depending on who I am talking to. One rep stated there is only one static public IP available for our use, another that there are 3 available, and in neither case did the IPs match 4 Public IPs I have found assigned to four different machines on the network which host incoming connections. (I am new to this situation, and the person who set this up is no longer with the company).
From what I have read elsewhere, and have been told by Nuvox, unlike static IP addresses from the cable company or the telco, there is some re-direction going on with most of the static IPs. Maybe this is where the problem is? Or maybe it is with the Zytel P310 broadband router, which is set to redirect the RDP port to the local ip but perhaps is not functioning correctly. At this point, I don't even know if the Zytel has the appropriate static WAN IP assigned in it.
Any guidance is much appreciated, I am uncertain exactly where the problem is.
Thanks,
Bill
I am having difficulty successfully setting up RDP connections to an office with a fractional T1 voice/data line provided by Nuvox Communications. The RDP host is funtional, as it can be accessed across the LAN, but not from outside. I am familiar with the router port forwarding requirements as I have about half a dozen computers on different networks which I set up and use via RDP. On several of them RDP utilizes a non-standard port other than 3389.
This is the only network which uses Nuvox for data/voice communications with the outside world, and I think this is where I am going wrong. The information I am getting from Nuvox regarding public static IP addresses is suspect, as it varies depending on who I am talking to. One rep stated there is only one static public IP available for our use, another that there are 3 available, and in neither case did the IPs match 4 Public IPs I have found assigned to four different machines on the network which host incoming connections. (I am new to this situation, and the person who set this up is no longer with the company).
From what I have read elsewhere, and have been told by Nuvox, unlike static IP addresses from the cable company or the telco, there is some re-direction going on with most of the static IPs. Maybe this is where the problem is? Or maybe it is with the Zytel P310 broadband router, which is set to redirect the RDP port to the local ip but perhaps is not functioning correctly. At this point, I don't even know if the Zytel has the appropriate static WAN IP assigned in it.
Any guidance is much appreciated, I am uncertain exactly where the problem is.
Thanks,
Bill
Rob Williams
Perhaps start by connecting to http://www.whatismyip.com from the PC to which you are trying to connect. This will tell you it's true, current, public IP. Verify that this is the IP with which you are trying to connect. If so, check all devices between you and the Internet to see that port forwarding is enabled. Sounds like you may have multiple routers between the PC and the Internet. Each will have to have the appropriate port forwarding configured.
ASKER
Thanks RobWill,
The WAN IP (according to www.mywanip.com) is the WAN IP address assigned to the router, and the address used in attempting to connect via RDP to the WIndows 2003 Server. I have tried routing both the default port of 3389 and a non-default port from the router to the server.
NEW INFO:
I was able, with no problem at all, to setup a connection using RealVNC, routing the VNC port to the server. So perhaps I need to be looking at something on the server. The terminal server role is NOT installed, and terminal services is running, same as other Windows 2003 servers I RDP into in other locations.
I also did a tracert to the router and to some external addresses, and found that in each case the route goes directly to the internal IP of the router, then to the external gateway address given us by our ISP, and on from there. There is another router on the network, but it appears to not be playing a role in this situation.
The WAN IP (according to www.mywanip.com) is the WAN IP address assigned to the router, and the address used in attempting to connect via RDP to the WIndows 2003 Server. I have tried routing both the default port of 3389 and a non-default port from the router to the server.
NEW INFO:
I was able, with no problem at all, to setup a connection using RealVNC, routing the VNC port to the server. So perhaps I need to be looking at something on the server. The terminal server role is NOT installed, and terminal services is running, same as other Windows 2003 servers I RDP into in other locations.
I also did a tracert to the router and to some external addresses, and found that in each case the route goes directly to the internal IP of the router, then to the external gateway address given us by our ISP, and on from there. There is another router on the network, but it appears to not be playing a role in this situation.
Where you can access the server through other services, and remote desktop works locally, it is very odd. A couple of thoughts:
>>"There is another router on the network, but it appears to not be playing a role in this situation."
The router on which you are configuring port forwarding is the default gateway for the server, I assume?? Actually must be if VNC works.
-At least as a test make sure the Windows (or any other software firewall) is disabled. They have different scopes/rules for local and Internet connections. Also check any virus protection suites than may include a firewall.
-If you haven't done so reboot the router in case a particular protocol is "locked up"
>>"There is another router on the network, but it appears to not be playing a role in this situation."
The router on which you are configuring port forwarding is the default gateway for the server, I assume?? Actually must be if VNC works.
-At least as a test make sure the Windows (or any other software firewall) is disabled. They have different scopes/rules for local and Internet connections. Also check any virus protection suites than may include a firewall.
-If you haven't done so reboot the router in case a particular protocol is "locked up"
ASKER
Oh, I was able to RDP locally to another machine (not the server), but then was not able to RDP to that machine from the outside, or to the server. Since then I have been focusing on the server. I will try the other machine again, though.
The router has been re-booted the other day.
The router has been re-booted the other day.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the advice,
I overlooked turning on remote access under system properties! What a simple oversight that has had me lost as to why I couldn't get connected. After that was corrected, policy also needed editing to allow remote users access, so that info was useful.
I overlooked turning on remote access under system properties! What a simple oversight that has had me lost as to why I couldn't get connected. After that was corrected, policy also needed editing to allow remote users access, so that info was useful.
Thanks Bill, glad it was of some help.
I made the list once as I find it's easy to look-over a little detail some times.
Cheers,
--Rob
I made the list once as I find it's easy to look-over a little detail some times.
Cheers,
--Rob