D-Link DIR-655 :: Utilize RDP (Windows Remote Desktop) Between Two Points
Jun 10, 2013
I recently purchased (2) DIR-655 routers; one for home and one for the office. Both are connected to the 'net through CenturyLink DSL via a Zyxel 660 modem.I am switching from a Cisco/Linksys WRT54G home and a Trendnet TEW432BRP at the office. I wanted to get up to N and consolidate to a single hardware type. The 655 came highly recommended, and the price was right at $75.My goal is to utilize RDP (Windows Remote Desktop) between the two points and from other points inbound to either 655. The first hurdle was that the Xyxel modem, by default, blocks just about everything inbound with no hope of opening the ports. The only viable solution was to bridge the modem and allow the 655 to act as DHCP. Done. The modem now should not even have its own IP address, and should completely bypass all of the built-in firewalls, etc. As soon as I went into bridged and forwarded the ports in the router we were in business (though I still can't seem to log in to RDP, the ports are verified open).
configure this router to allow connections from the internet for remote desktop? I can do it on my lan, but the Dir-825 blocks this feature. Yes, I set up port 3389 as a virtual server to the computer I wish to use.
I have a Win 7 machine with Win SBS 2011 in my office and an iMac. The Win machine is being setup for Exchange 2010. My problem is this: I can't Remote Desktop in from my iMac into the Win machine, but CAN when outside the network.The Win7 machine has a static IP, the iMac a dynamic. When I access the internal part of my router I can only see my iMac. I get a "can't connect to win-based machine" error when I try to Remote Connect.The only thing I can think is that using the same gateway is somehow messing things up? I've had two techs try to figure this out and they're both stumped.I was maybe thinking that since both comps are going out the same gateway that I should try anc configure the iMac to try and RDC on a different port, since maybe the iMac is listening on 3389 and sending the RDC back to itself?
We have a WRSV4400N installed as our primary NAT Firewall. It is configured to allow Windows VPN connections to our server residing on the Internal Network Domain - this works fine.Problem is that even though the remote VPN client can open shares, browse the internal network, and resolve computer names fine with DNS, but... Remote Desktop will not connect using the VPN tunnel.We need this to work... I spent several hours with your support people when installing this router a year ago and got nowhere. And everythung else works fine.I am using Windows server-based VPN because your VPN Clint didn't work ata ll either. Can you perhaps give me a list of configuration settings to check?
we just got several laptops that came with Windows 7 Pro 32bit installed, and we have installed the VPN Client 5.0.06.0110. The VPN client appears to connect to our ASA5510, but we are unable to connect to any machines on our network as it does on our XP machines.
Furthermore, we cannot ping any as well. Also, while connected the Windows 7 machine is still able to access internet site as if split-tunneling was configured, which its not! I've seen alot of people posting on the internet about the same issue, but I have not run into any resolutions that work.
I have a home network and I routinely connect from my laptops to my wired desktop via Remote Desktop. Routinely, that is, until I replaced my old wireless router with a D-Link Wireless N router. But now, after the change, I can no longer remote desktop in. I *am* able to ping and file share with that computer, just no remote desktop.
I use RDP extensively on my LAN to use and manage 4 PCs running Win XP or Win7. My consumer-grade Cisco Linksys WRT610n crapped out after less than 2 years, so I thought I'd try the Cisco WRVS4400N to gain extra features like VPN. I have not enabled anything new on the router except for adding a second wireless SSID for guest use, although no bandwidth management or VLANs have been set up yet. Firmware version is 126.96.36.199.Since installing this router I have been unable to use Windows RDP on ANY of my computers on the LAN, whether I use the machine name or the IP address. I can ping every device on my network - print servers, NAS boxes, PCs, but no RDP. WHAT'S GOING ON?
I am attempting to set up a remote desktop connection to my home media server so I no longer need to keep a keyboard, mouse, and monitor plugged in to it when I need to use it. I am running Windows 7 Home Premium on both systems. I am sure the firewall is not the problem, as I have tried to connect with it disabled. I have also made sure to allow remote connections on the server. I know the DIR-825 supports UPnP, which works with Remote Desktop, so there should be no problem, but something is not working. I have tried disabling UPnP, setting up a virtual server, port forwarding, and assigning a permanant IP to the server, to no effect. Something is blocking my remote connection requests. Keep in mind, I am not even trying to do this over the internet, just over my LAN!
I just picked up the E4200 to replace a router, I can remote desktop into a computer that is physically connected to this router, but cannot remote desktop into other computers on the network that are connected via another switch.
I opened the remote management to my Dir 655 but i can't enter it I tried to change port it didn't work, tried to factory defaults or hard reset didn't work what can i do I think it all so stuck my access to my remote desktop (not sure)
Region : UnitedKingdom Model : TD-W8968 Hardware Version : V1 Firmware Version : 1.0 ISP :
I recently bought this modem for use at home. When I try to log in to my computer at work I am able to log in to the server via a VPN connection but not onto individual computers via Remote Desktop Connection. Both computers run windows 7.
I was using Remote Desktop between two home computers hard wired through the router and a switch. Now after upgrading to firmware 1.35 I can't get remote desktop to connect. I get an error that I may not have permission, etc. I have the DIR 655 ver A and am running Windows 7 professional on both computers.
Region : India Model : TL-WR740N Hardware Version : V4 Firmware Version : 3.12.11 Build 120320 Rel.51047n ISP : BSNL
I am facing some issue in LAN network.I have connected one desktop( win 7) and another desktop (win xp) to the TP link router. Both the computers got ip address and able to share the internet. But both the computers are not in the same network. That is they cant PING each other. hence they are not visible to each other.
On wireless (lenovo tabletx61) I cannot connect through the intranet - no problem connecting through internet. When I manage to connect through intranet connection is dropped quite often.No problem connecting via Ethernet cables.
I'm trying to connect to my home laptop from work. The home laptop is connected to DIR-655 router. I set up the internal and external ports to 3389 using both TCP and UDP protocols with the Application as "Remote Desktop". From my work PC I enter the external IP with :3389 and it fails to connect. I have also tried accessing internally which is failing too. All computers are running Windows 7 Home Premium Remote Access is enable on all.
i have deployed WLC 5508 in head office with current 56 access points (mix of 1262N, 1141N and 1242) are regist ered and working fine, recently we extended to our remote office (connected over Layer 3 MPLS with OSPF Protocol) were none of the access points are not registering, i am able to reach to the controller from the specific VLAN and native VLAN without any issues. @remote site i have enabled option 43 and option 60 with the controller IP.
Number of APs.................................... 56 Global AP User Name.............................. ciscoGlobal AP Dot1x User Name........................ Not Configured
Have just been trying to install Remote Desktop between two XP pro laptops When I try to log on I get a black screen with the connection bar at the top with the name of the remote computer and after about thirty seconds it drops the connection. The remote laptop comes up with logon screen but it isn't visible on the on host machine.I have followed all the instructions including file sharing enabled remote accesss etc, Both machines show up on network map and can ping each other.
To use Remote Desktop Connection, is it really this easy:Open up remote desktop connection on your Host PC --- type the IP of the computer you want to access, then click connect --- As long as "Allow Remote Desktop" is enabled on the PC you are trying to connect to, your attempt will be successful
We have a server which in addition to other services is used to stream live hi-def video from our building during special events.We use a software video/audio production mixer which works very well. But we now would like to make a change in the system.Is it possible/practical to use Remote Desktop via the second - as yet unused - LAN in our server. We really would like to put the operators in a different location where they have both video and in-person view of the event being streamed. But we don't want to use more bandwidth on the LAN...the production mixer handles a *lot* of uncompressed video and tends to be a bandwidth hog.
We use Nortel VPN and the problem is that it's set so when you connect to it, you can only access company resources so no Internet. To mitigate that we use vmware and run Windows XP at the same time as our Windows 7 systems. I'd love to be able to use remote desktop though and connect to a system located elsewhere even another office computer and have that one on the VPN, but of course as soon you connect the remote desktop connection goes down with it.I'm just wondering if there's any ways around this. I'm assuming not, but I'm not sure how VPN fully works. Like if I had 2 network cards in the remote system, when I VPN in does it block connections from all network cards? Ideally I'd like to use something like Amazon Web Services since their Windows Server tier has the free option which is good, or will use another VPS type system running Windows Server.
I opened a computer in other network via remote desktop(because I forwarded port in router)....and tried to access other computers in the network via remote desktop again from that computer but after I done, I don't know how to close the secondary remote desktop. There was one close button on the top, but if "close" it, whole rdp connection was closed. The secondary rdp connection is still open in the computer.
I have a PC behind a DSL router. In my PC (WinXP SP3) I have a virtual machine also running WinXP SP3. I would like to access the VM via remote desktop. Since I have a dynamic IP, I use the(url)tool to solve the problem. I installed the no-ip sync tool in the VM. Now when I write my no-ip address in the remote desktop from my office, I will access my host system, and not the hosted VM. Does any knows how I should configure things in order to get access to the virtual machine and not to the host machine
I have some iMacs that I manage for, in addition to my primary PC computers, such as my Toshiba Windows 7 laptop, which is what I am currently most concerned with. What I would like to do, is Remote Desktop Control (I'll abbreviate that as RDC) these mac computers through the network from my Windows PC. I am aware that this is possible with either Google Chrome, or by checking an OSX setting that will allow for VNC applications to connect, but I would prefer it if there was some way to RDC these iMacs from my Windows laptop without needing to change their settings or install software-something like how Mac-Mac RDC connections work, where I can just select a computer from the network, type a password, and go.
Basically, I rebuilt my network over the weekend, to include a subnet, and can no longer connect my desktop to the remote PC. My old router was reset to defaults and re-configured. My PC has been wiped, reinstalled, and fully updated.The error I receive is "Remote Desktop can't connect to the remote computer for one of these reasons: etc" I've only seen this error in the past when the PC I connect to was powered down. I have confirmed that everything is still set up properly on the PC I'm trying to connect to via an associate, and it is not powered down.
1. I went into Windows firewall to allow Remote Desktop through, but it looks like that only needs to be set for the PC I'm trying to connect to. (Yes/No?)
2. I've forwarded port 3389 from the old router to my PC.
3. I haven't done anything yet to the new router, because I really can't tell if I'm doing the right things. The very first time I connected to the remote PC, it went right through, and I didn't have to change anything in the old router (I think - it's been awhile). I really don't know where to go from here, and it looks like the setup options I've found in the forum so far (static IP, port forwarding, Windows firewall changes, etc.) leave me with more security risks than I had on the old network, and there seem to be some conflicting opinions about the setup process.