Timeline for Windows Remote Desktop fails through VPN until browsing to network share
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 20, 2015 at 19:54 | vote | accept | BurnsBA | ||
| Aug 20, 2015 at 19:54 | answer | added | BurnsBA | timeline score: 0 | |
| Apr 8, 2015 at 16:31 | history | edited | BurnsBA | CC BY-SA 3.0 |
os info
|
| Apr 8, 2015 at 15:48 | comment | added | BurnsBA | Doesn't seem to be any difference using name or IP. | |
| Apr 8, 2015 at 15:46 | history | edited | BurnsBA | CC BY-SA 3.0 |
deleted 10 characters in body
|
| Apr 8, 2015 at 15:45 | comment | added | BurnsBA | TELNET doesn't work before browsing network share. Remote desktop has stopped connecting (it was fine a minute ago) so I'm not sure about the "after." | |
| Apr 8, 2015 at 15:40 | history | edited | BurnsBA | CC BY-SA 3.0 |
telnet
|
| Apr 8, 2015 at 15:21 | comment | added | Patrick | Connect the VPN then try TELNET 10.20.30.40 3389, this should connect you to a black screen. It will demonstrate that the connection is up and the port is available. Frankly what you are describing doesn't make much sense to me. If TELNET fails then its a timing issue. Try the telnet before browsing the share and then after. | |
| Apr 8, 2015 at 15:20 | comment | added | Ƭᴇcʜιᴇ007 | Are you trying to connect to the remote machine via name or IP? If it's by name, try using the RDP host's IP address instead (also try using its FQDN). | |
| Apr 8, 2015 at 15:14 | history | asked | BurnsBA | CC BY-SA 3.0 |