|
|
Question : Remote Desktop/Networking Question
|
|
Hello. I am a bit of a novice, but I really need to find an answer. We just installed a Cisco ASA 5510 with VPN. We are running the VPN with IPSec, not SSL. Our network is currently peer to peer TCP/IP with NetBUEI running on our main file server. This file server is running Windows Server 2000.
I have been able to access my work computer from my home computer via Remote Desktop. However, I got disconnected for some reason a few days ago during a session. After that, I can still connect through the VPN with no problem, but I am getting the following message when I log into remote desktop:
The client could not connect to the remote computer. Remote connections might not be enabled or the computer might be too busy to accept new connections. It is also possible that network problems are preventing your connection. Please try connecting again later. If the problem continues to occur, contact your administrator
Remote connections are enabled. Windows firewall exceptions have been made. Our Cisco firewall is letting me in, but Remote Desktop is not letting me get to my computer.
I should also mention that I cannot use computer names with RD, only IP addresses (not sure why&NetBUEI maybe?). I also attempted to use RD in house from my work computer to another users computer (making sure that Remote connections were enabled and Windows firewall exceptions had been allowed) and I got the same results.
Does anyone have any thoughts?
|
Answer : Remote Desktop/Networking Question
|
|
Glad you nailed it... Seems like a basic routing issue.... The route was rebuilt with the Wired card only present, and RDP could find the host.... Some apps are finicky that way, have never experienced it though, myself...
|
|
|
|
|