Remote Desktop Connection behind 2 routers
We have a buisness VOIP phone setup with a DLINK router. The DLINK router connects to a port on the VOIP hub and that port supplies internet. I have port forward setup in the DLINK for remote desktop on port 3389 that directs to the server. I have also contacted the phone company to open port 3389 to the DLINK's gateway. I still can not get into the server through remote desktop. I have disabled the firewall on the server. Can someone please direct me in the right direction as to what I need to do next? Also I am running Server 2003 Standard R2
Thanks in advance
Thanks in advance
Last Comment
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Sorry typo mean to say VoIP device nor dlink
In final paragraph
Apologies (on iPhone)
In final paragraph
Apologies (on iPhone)
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
I can rdp internally. The way the setup is:
Internet--->VOIP modem---->DLINK Router---->Server. The VOIP Modem is controlled by the cable/phone company. I have no access to the VOIP modem. The VOIP is a router. The gateway for the DLINK is 192.168.0.1. I have had the cable company open up port 3389 TCP traffic to 192.168.0.1. I am going to say that the DLINK performs IP NATing. The VOIP Modem is directly connected to the internet through fiber optics. Thanks for the help!
Also to answer the first comment, I can not change the line up, I wish I could, but the VOIP modem has the fiber optics comming into it.
Internet--->VOIP modem---->DLINK Router---->Server. The VOIP Modem is controlled by the cable/phone company. I have no access to the VOIP modem. The VOIP is a router. The gateway for the DLINK is 192.168.0.1. I have had the cable company open up port 3389 TCP traffic to 192.168.0.1. I am going to say that the DLINK performs IP NATing. The VOIP Modem is directly connected to the internet through fiber optics. Thanks for the help!
Also to answer the first comment, I can not change the line up, I wish I could, but the VOIP modem has the fiber optics comming into it.
Did you try enabling remote management on your router and see if you can access it using your remote address.. I'm also assuming that you forwarded port 3389 on the dlink router to your local computers ip address.
ASKER
No I have not had a chance to enable remote management, I will do that tomorrow when I get to the office and post an update. And yes I have pointed port 3389 to the servers address.
ASKER
Ok I accepted everyones answers because they all were very informational and they were directing me in the right direction, but we finally resolved this issue by getting our cable company representative on site with me and we change the whole setup and we now have the VOIP router handling dhcp and were using the wireless router as access point only. Thats the initial way I would had set it up, but after talking with him multiple times, we came up with this solution, so now I can use remote desktop. I gave best answer to "ve3ofa" because "ve3ofa" pointed out it is probably in the VOIP modem and "ve3ofa" was correct. Thank you all for your help on this.
Windows Server 2003
Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
If your certain the dlink has both a firewall rule allowing the port inbound and a port forward to the correct ip of the server
Then it could be your providers have not done likewise on the dlink (Ie allow port inbound traffic to be forwarded to the gateway ip ?