![]() Only after rebooting and login in to windows PC1 from clients to RDC first solved problem 2. After login in to windows NR server start normally, NR network is operating OK, but again same problems with connection to PC1 from clients using RDC: after login in to remote windows screen goes blank and after a while RDC disconnects.ĭoing log off from PC1 windows and connecting to it from clients doesn't helped. After reboot without login in to windows NR server doesn't starts.Ģ. ![]() Finally was not asked to reboot, but did this. Then, without rebooting PC1, continued the new version installation. Did this with saving configuration files. During installing new version was asked first to remove previous version. release last week.īut with PC1 with NR server had some. Logged off the office PC3 from console (not remotely) and now no problem to connect with RDC from PC1 and PC2. So it seems problem can reoccur even without logging off or rebooting. The same time no problems to access with RDC PC3 from PC2.Īfter a few hours the problem occurred even with access with RDC PC3 from PC2. Office PC3 complete reboot didn't helped too. I have loged off user from office PC3 and still can't connect to it with RDC from PC1. Strange, my another PC2 just now connected with RDC to office PC3 without problems! So, as I understand the flow, for RDC to operate properly after neorouter installed on remote PC you need at least once connect to it with RDC then it is booted but no single user is logged on.Seems not, see edits below. Just now at home discovered that the same problem is with accessing my office PC3 from PC1. PC3 WinXP Pro, WAN, domain, neorouter explorer installation PC2 WinVista HP, LAN, workgroup, neorouter explorer installation PC1 WinXP Pro, LAN, workgroup, neorouter server installation Mostly you need to close RDC and even reconnect to neorouter network (restart remote client if using portable) to reconnect with RDC to remote PC again.Īny suggestions/clarification on these cases? RDC loosing connection and try to reconnect, but succeed very rarely. Often minimizing RDC and trying to reuse it after some time (>10 min.) is impossible. Minimum = 0ms, Maximum = 202ms, Average = 10msĭisabling of RDC bitmap caching did not helps.Ģ. Packets: Sent = 19677, Received = 19573, Lost = 104 (0% loss),Īpproximate round trip times in milli-seconds: The overall network perfomance is OK, just in line with hamachi: Reply from 10.0.0.1: bytes=32 time=38ms TTL=128Īccess to the network shares of remote PC (including shares requiring login) is OK. ![]() After RDC disconnecting, pinging goes OK again: Pinging during RDC connection shows host ping delays and request timed out in the moment of login to remote PC. Sometimes after entering username and password remote PC's desktop starting to appear but then again freezes and RDC disconnecting in about a minute. Problem details: RDC connecting to remote PC, windows logon screen appearing, after entering username and password screen goes black and stays for about a minute, then RDC desconnecting. Using NeoRouter portable remote desktop connection is OK but unstable (another problem, will discuss later). Getting problem to connect with Microsoft Remote desktop client (RDC) to PC with NeoRouter server from both LAN and WAN PCs using NeoRouter installation. Neoroute server is on the WinXP Pro Lan with properly forwarded ports on hardware router (Dashboard test is green OK). The neoroute net is up (all hosts pinging each other OK) with 3 PC WinXP Pro (2PC on WAN, 1PC on LAN) + 1 PC Vista HP on LAN. Was using hamachi for a 3-4 yeras before, now trying to neoroute and got some problems.ġ. First, let me to thank you for the great product!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |