cancel
Showing results for 
Search instead for 
Did you mean: 

Remote Desktop Connection error with HT2000W

pswired
Junior

Re: Remote Desktop Connection error with HT2000W

@tracerrx are you on a beam that has congestion issues? One thing I've noticed is that during periods of extreme congestion/packet loss on the satellite link, the web acceleration process on the HT2000W will die, presumably due to needing 2-way IP communication with the gateway and some sort of watchdog timing out. Peraps there is some other connection-based timeout for the IPv4 over IPv6 tunnel back to the CGN device that runs out during periods of heavy packet loss and congestion, causing the behavior we're seeing? 

C0RR0SIVE
Associate Professor

Re: Remote Desktop Connection error with HT2000W

@Liz@tracerrx and I decided to perform some troubleshooting together, we have plans on doing some more soon when our schedules are clearish during peak hours when this seems to be more of an issue.

The testing is a little different from how everyone is setup, as the goal was to see if it could be some form of routing issue.

I have a Static Business account, and decided to setup an RDP server behind that.  I then asked @tracerrx to remotely connect to my site with various differen't connections that he has available.  We didn't get to do much, as by the time we started I had already been up for a good 24+ hours, however, we didn't run into issues during the testing period.  Granted this is very different from how others are using RDP with Hughesnet (they are remoting into work, we remoted the opposite direction people would normally go...).

The next test phase will involve my Static Business Account connecting into a server setup by @tracerrx to see if it disconnects, and perform these tests again during peak usage hours, we will also test a normal Residential Account to see if either experience strange behavior.

We are still trying to determine if the IPv6 address change is causing the issue (hence the SME testing, since it's static IPv4), but, we have yet to see the address change during our limited testing.

Tracers Work Log:

Connected Via RDP from Comcast at 12:15EST

I truly cant belive how slow this is and that people try and use this for work!

going to run MTR from my machine on the connection as well.. Will paste results here:

Wow.. some serious packet loss going on at L3, 
                             My traceroute  [vUNKNOWN]
NMS-MacBook-Pro-2015.local (XXX.XXX.XXX.140)                  2017-12-09T12:25:55-0500
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                           Packets               Pings
 Host                                    Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. TracerRT                              0.0%    38    9.1   7.0   2.6  16.2   3.2
 2. XXX.XXX.XXX.XXX                       0.0%    37   27.9  21.5  11.7  59.9   9.3
 3. xe-0-2-1-sur01.westboca.fl.pompano.c  0.0%    37   19.5  19.5  12.8  35.6   5.3
 4. xe-11-1-1-0-sur02.westboca.fl.pompan  0.0%    37   15.9  20.4  12.1  52.6   8.3
 5. ae-5-ar02.stuart.fl.pompano.comcast.  0.0%    37   61.5  25.8  13.4  61.5   8.0
 6. hu-0-12-0-6-ar01.northdade.fl.pompan  0.0%    37   25.2  28.1  20.3  85.9  10.4
 7. ae13.edge2.miami1.level3.net         40.5%    37   23.8  28.3  19.8  66.3   9.6
 8. ae-1-3505.ear1.losangeles1.level3.ne 88.9%    37   90.8  87.9  85.2  90.8   2.3
 9. hughes-netw.ear1.losangeles1.level3.  0.0%    37   83.5  89.2  82.1 122.6   7.1
10. host17433001205.direcway.com          0.0%    37   89.6  89.3  82.4 100.8   4.6
11. ???
12. C0RR0SIVE SME RDP Server                  0.0%    37  686.6 686.8 638.6 739.8  24.4


Just thinking that I should have spun up a VM and let you connect with diff modems... I hate burning through your data cap!

12:40pm.. Still Connected... 
12:57pm... still all good, no disconnects
1:08pm... not a single disconnect.. switching over to hughes BRB
1:11pm Connected directly to hughes modem via ethernet... Holy cow is this slow! Reminds me of typing on an appletalk 300baud modem!

Wow.....MTR 
    My traceroute  [vUNKNOWN]
NMS-MacBook-Pro-2015.local (XXX.XXX.XXX.140)                2017-12-09T13:13:05-0500
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                           Packets               Pings
 Host                                    Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. TracerRX                              0.0%    27    0.3   0.4   0.3   0.5   0.0
 2. XXX.XXX.XXX.XXX                       0.0%    27    0.6   0.5   0.4   0.7   0.1
 3. host9772157.direcpc.com               0.0%    27  666.6 609.6 555.7 666.6  29.8
 4. host9772461.direcpc.com               0.0%    27  577.8 604.6 549.0 675.9  30.6
 5. phn4-edge-03.inet.qwest.net           3.8%    27  672.7 603.5 548.3 672.7  32.2
 6. los-brdr-02.inet.qwest.net            3.8%    27  611.8 613.7 551.4 682.0  29.0
 7. 63-235-41-122.dia.static.qwest.net   80.8%    26  623.4 628.1 616.1 648.5  12.1
 8. ae-2-3605.ear1.losangeles1.level3.ne 84.0%    26  654.3 612.2 591.8 654.3  29.0
 9. hughes-netw.ear1.losangeles1.level3.  3.8%    26  639.6 620.1 563.5 734.6  34.0
10. host17433001205.direcway.com          3.8%    26  660.8 619.4 551.8 684.4  33.6
11. ???
12. C0RR0SIVE SME RDP Server                  3.8%    26  1231. 1171. 1098. 1231.  39.3


1:15pm still connected, but latency is so high!
1:28pm... still PAINFULLY connected
1:59pm... Still Connected
2:15pm... Still Connected
2:37pm... Server disconnected (c0rr0sive closed ports)

I think we will retest the test we have already done (connecting back to a Hughesnet account hosting RDP) during peak hours, then at a later date if nothing happens, retest in the normal fashion, going from a Hughes terminal to an RDP server.


@pswired, the Web Acceleration server *shouldn't* impact RDP at all, it's used only for HTTP/S connectivity.  Though, if the modem bugs out because of a WAS issue, that in it self *could* impact connectivity, but I suspect that would be impacting all protocols.

Liz
Moderator
Moderator

Re: Remote Desktop Connection error with HT2000W

Hi C0RR0SIVE, 

 

Thanks for looking into this, this could be useful for engineering. Speaking of which, has someone reached out to you about that on FB?

 

If you have a tech or billing question and need help, please start a new thread in the appropriate board. Unsolicited Private Messages may not get replies.

Slow performance? Click me!

tracerrx
Sophomore

Re: Remote Desktop Connection error with HT2000W

@pswired thats an interesting theory... you can cleary see the congestion in MTR... I was assuming that it was between 2 Level-3 edge routers... but its possible they are dedicated/leased to hughes... At one point was seeing 90% drops consistently... However it did not seem to be effecting performance

C0RR0SIVE
Associate Professor

Re: Remote Desktop Connection error with HT2000W

@Liz

Yes, several have over the months. They seem to enjoy poking me ever time I post in this thread, it might be bad for my health long term. Smiley Happy lol

Know the whole, "dont disturb an engineer" thing?  I am quiet possibly more skiddish than they are when they poke me Smiley Happy

P7UBqAr.jpg

This is mostly additional testing that I am performing to see if I, or the community can actually pinpoint a probable cause that can be replicated in some fashion.


eranch
Freshman

Re: Remote Desktop Connection error with HT2000W

@Liz I am having this same problem. No problems until I upgraded to Gen 5 in August. Support is absolutely no help. They don't seem to know that this problem exists. Terrible. Please add me to the escalation ticket you have ongoing with your engineers. Just as many have stated, I use remote desktop for work every single day. If I had another internet option, I would be gone. HughesNet should be crediting us something on our bills until this issue is resolved.

C0RR0SIVE
Associate Professor

Re: Remote Desktop Connection error with HT2000W

So, decided to do some solo testing... @Liz this may be of help to the engineers...

Decided to test from a residential unit to a remote server hosted on a land-line connection, started the test at approximately noon today, and at 3:30 (15:31) I recieved an encryption error.  I decided to check my router for any potential errors, none.  Checked the HT2000w, and saw nothing something that actually stood out while pasting the log into here.

 

I MAY have found the issue, and it certainly is an issue with WAN side IPv4 addressing, unsure of the IPv6, as the error is strictly talking about IPv4 at the disconnect.  Highlighted in bright bold red below 3 errors that occured at the exact time that RDP failed.

I WILL be testing this again to see if the same error condition occurs, as I do want to see this resolved for the ones that use RDP frequently, and I want to make sure this is what is actually happening.

Dec 11 15:32:43 (none) daemon.info dhclient: bound to 100.74.83.170 -- renewal in 57 seconds.
Dec 11 15:32:43 (none) daemon.info dhclient: [bind_lease:1581] dhclient bind lease.
Dec 11 15:32:40 (none) daemon.info dhclient: [gratuitous_arp:125] dhclient gratuitous arp.
Dec 11 15:32:40 (none) daemon.info dhclient: [dhcpack:1394] dhclient receive ack from server(100.74.83.169).
Dec 11 15:32:40 (none) daemon.info dhclient: DHCPACK from 100.74.83.169
Dec 11 15:32:40 (none) daemon.info dhclient: [send_request:2730] dhclient send request.
Dec 11 15:32:40 (none) daemon.info dhclient: adapter index 6
Dec 11 15:32:40 (none) daemon.info dhclient: adapter index 6
Dec 11 15:32:40 (none) daemon.info dhclient: DHCPREQUEST on eth0.2 to 100.74.83.169 port 67
Dec 11 15:32:27 (none) daemon.info dhcpd: DHCPACK on 192.168.10.11 to 00:0c:29:b5:86:e2 (pfS1) via br0
Dec 11 15:32:27 (none) daemon.info dhcpd: DHCPREQUEST for 192.168.10.11 from 00:0c:29:b5:86:e2 (pfS1) via br0
Dec 11 15:32:11 (none) user.debug syslog: command_handler(607):There is not WAN to be specified, use wan_dft_idx 0.
Dec 11 15:32:11 (none) user.debug syslog: command_handler(566):arca.dbus.dhcp6c: @@received command: CMD_START
Dec 11 15:32:11 (none) daemon.info arc_monitor: excute action:monitor_dhcp6c
Dec 11 15:32:11 (none) daemon.info arc_monitor: process radvd: IPv6 settings is not ready!
Dec 11 15:32:11 (none) daemon.info arc_monitor: process dhcp6d: IPv6 settings is not ready!
Dec 11 15:32:11 (none) daemon.info arc_monitor: Process escaped last time, set action:monitor_dhcp6c to restart
Dec 11 15:32:11 (none) daemon.info arc_monitor: Process dhclient6 is not found!
Dec 11 15:31:43 (none) daemon.info dhclient: bound to 100.74.83.170 -- renewal in 57 seconds.
Dec 11 15:31:43 (none) daemon.info dhclient: [bind_lease:1581] dhclient bind lease.
Dec 11 15:31:40 (none) daemon.info dhclient: [gratuitous_arp:125] dhclient gratuitous arp.
Dec 11 15:31:40 (none) daemon.info dhclient: [dhcpack:1394] dhclient receive ack from server(100.74.83.169).
Dec 11 15:31:40 (none) daemon.info dhclient: DHCPACK from 100.74.83.169
Dec 11 15:31:40 (none) daemon.info dhclient: [send_request:2730] dhclient send request.
Dec 11 15:31:40 (none) daemon.info dhclient: adapter index 6
Dec 11 15:31:40 (none) daemon.info dhclient: adapter index 6
Dec 11 15:31:40 (none) daemon.info dhclient: DHCPREQUEST on eth0.2 to 100.74.83.169 port 67
Dec 11 15:31:33 (none) user.debug syslog: mid_mng_get(303):MNG Get: [ARC_WAN_0_IP4_Addr_2] Fail
Dec 11 15:31:30 (none) user.debug syslog: mid_mng_get(303):MNG Get: [ARC_WAN_0_IP4_Addr_2] Fail
Dec 11 15:31:11 (none) user.debug syslog: command_handler(607):There is not WAN to be specified, use wan_dft_idx 0.
Dec 11 15:31:11 (none) user.debug syslog: command_handler(566):arca.dbus.dhcp6c: @@received command: CMD_START
Dec 11 15:31:11 (none) daemon.info arc_monitor: excute action:monitor_dhcp6c
Dec 11 15:31:11 (none) daemon.info arc_monitor: process radvd: IPv6 settings is not ready!
Dec 11 15:31:11 (none) daemon.info arc_monitor: process dhcp6d: IPv6 settings is not ready!
Dec 11 15:31:11 (none) daemon.info arc_monitor: Process escaped last time, set action:monitor_dhcp6c to restart
Dec 11 15:31:11 (none) daemon.info arc_monitor: Process dhclient6 is not found!
Dec 11 15:31:10 (none) user.debug syslog: mid_mng_get(303):MNG Get: [ARC_WAN_0_IP4_Addr_2] Fail
Dec 11 15:30:43 (none) daemon.info dhclient: bound to 100.74.83.170 -- renewal in 57 seconds.
Dec 11 15:30:43 (none) daemon.info dhclient: [bind_lease:1581] dhclient bind lease.
Dec 11 15:30:40 (none) daemon.info dhclient: [gratuitous_arp:125] dhclient gratuitous arp.
Dec 11 15:30:40 (none) daemon.info dhclient: [dhcpack:1394] dhclient receive ack from server(100.74.83.169).
Dec 11 15:30:40 (none) daemon.info dhclient: DHCPACK from 100.74.83.169
Dec 11 15:30:40 (none) daemon.info dhclient: [send_request:2730] dhclient send request.
Dec 11 15:30:40 (none) daemon.info dhclient: adapter index 6
Dec 11 15:30:40 (none) daemon.info dhclient: adapter index 6
Dec 11 15:30:40 (none) daemon.info dhclient: DHCPREQUEST on eth0.2 to 100.74.83.169 port 67
Dec 11 15:30:11 (none) user.debug syslog: command_handler(607):There is not WAN to be specified, use wan_dft_idx 0.
Dec 11 15:30:11 (none) user.debug syslog: command_handler(566):arca.dbus.dhcp6c: @@received command: CMD_START
Dec 11 15:30:11 (none) daemon.info arc_monitor: excute action:monitor_dhcp6c
Dec 11 15:30:11 (none) daemon.info arc_monitor: process radvd: IPv6 settings is not ready!
Dec 11 15:30:11 (none) daemon.info arc_monitor: process dhcp6d: IPv6 settings is not ready!
Dec 11 15:30:11 (none) daemon.info arc_monitor: Process escaped last time, set action:monitor_dhcp6c to restart
Dec 11 15:30:11 (none) daemon.info arc_monitor: Process dhclient6 is not found!
Dec 11 15:29:42 (none) daemon.info dhclient: bound to 100.74.83.170 -- renewal in 57 seconds.
Dec 11 15:29:42 (none) daemon.info dhclient: [bind_lease:1581] dhclient bind lease.
Dec 11 15:29:39 (none) daemon.info dhclient: [gratuitous_arp:125] dhclient gratuitous arp.
Dec 11 15:29:39 (none) daemon.info dhclient: [dhcpack:1394] dhclient receive ack from server(100.74.83.169).
Dec 11 15:29:39 (none) daemon.info dhclient: DHCPACK from 100.74.83.169
Dec 11 15:29:39 (none) daemon.info dhclient: [send_request:2730] dhclient send request.
Dec 11 15:29:39 (none) daemon.info dhclient: adapter index 6
Dec 11 15:29:39 (none) daemon.info dhclient: adapter index 6
Dec 11 15:29:39 (none) daemon.info dhclient: DHCPREQUEST on eth0.2 to 100.74.83.169 port 67
Dec 11 15:29:11 (none) daemon.err httphsc[7293]: open local socket error
Dec 11 15:29:11 (none) daemon.err httphsc[7293]: connect error, errno=[11]
Dec 11 15:29:09 (none) user.debug syslog: command_handler(607):There is not WAN to be specified, use wan_dft_idx 0.
Dec 11 15:29:09 (none) user.debug syslog: command_handler(566):arca.dbus.dhcp6c: @@received command: CMD_START
Dec 11 15:29:09 (none) daemon.info arc_monitor: excute action:monitor_dhcp6c
Dec 11 15:29:09 (none) daemon.info arc_monitor: process radvd: IPv6 settings is not ready!
Dec 11 15:29:09 (none) daemon.info arc_monitor: process dhcp6d: IPv6 settings is not ready!
Dec 11 15:29:09 (none) daemon.info arc_monitor: Process escaped last time, set action:monitor_dhcp6c to restart
Dec 11 15:29:09 (none) daemon.info arc_monitor: Process dhclient6 is not found!
Dec 11 15:28:50 (none) kern.warn kernel: [272060.220000] [wifi1] FWLOG: [10163793] WAL_DBGID_SECURITY_MCAST_KEY_SET ( 0x2 )
Dec 11 15:28:42 (none) daemon.info dhclient: bound to 100.74.83.170 -- renewal in 57 seconds.
Dec 11 15:28:42 (none) daemon.info dhclient: [bind_lease:1581] dhclient bind lease.
Dec 11 15:28:39 (none) daemon.info dhclient: [gratuitous_arp:125] dhclient gratuitous arp.
Dec 11 15:28:39 (none) daemon.info dhclient: [dhcpack:1394] dhclient receive ack from server(100.74.83.169).
Dec 11 15:28:39 (none) daemon.info dhclient: DHCPACK from 100.74.83.169
Dec 11 15:28:39 (none) daemon.info dhclient: [send_request:2730] dhclient send request.
Dec 11 15:28:39 (none) daemon.info dhclient: adapter index 6
Dec 11 15:28:39 (none) daemon.info dhclient: adapter index 6
Dec 11 15:28:39 (none) daemon.info dhclient: DHCPREQUEST on eth0.2 to 100.74.83.169 port 67
Dec 11 15:28:09 (none) user.debug syslog: command_handler(607):There is not WAN to be specified, use wan_dft_idx 0.
Dec 11 15:28:09 (none) user.debug syslog: command_handler(566):arca.dbus.dhcp6c: @@received command: CMD_START
Dec 11 15:28:09 (none) daemon.info arc_monitor: excute action:monitor_dhcp6c
Dec 11 15:28:09 (none) daemon.info arc_monitor: process radvd: IPv6 settings is not ready!
Dec 11 15:28:09 (none) daemon.info arc_monitor: process dhcp6d: IPv6 settings is not ready!
Dec 11 15:28:09 (none) daemon.info arc_monitor: Process escaped last time, set action:monitor_dhcp6c to restart
Dec 11 15:28:09 (none) daemon.info arc_monitor: Process dhclient6 is not found!
Dec 11 15:27:42 (none) daemon.info dhclient: bound to 100.74.83.170 -- renewal in 57 seconds.
Dec 11 15:27:42 (none) daemon.info dhclient: [bind_lease:1581] dhclient bind lease.
Dec 11 15:27:39 (none) daemon.info dhclient: [gratuitous_arp:125] dhclient gratuitous arp.
Dec 11 15:27:39 (none) daemon.info dhclient: [dhcpack:1394] dhclient receive ack from server(100.74.83.169).
Dec 11 15:27:39 (none) daemon.info dhclient: DHCPACK from 100.74.83.169
Dec 11 15:27:39 (none) daemon.info dhclient: [send_request:2730] dhclient send request.
Dec 11 15:27:39 (none) daemon.info dhclient: adapter index 6
Dec 11 15:27:39 (none) daemon.info dhclient: adapter index 6
Dec 11 15:27:39 (none) daemon.info dhclient: DHCPREQUEST on eth0.2 to 100.74.83.169 port 67
Dec 11 15:27:09 (none) user.debug syslog: command_handler(607):There is not WAN to be specified, use wan_dft_idx 0.
Dec 11 15:27:09 (none) user.debug syslog: command_handler(566):arca.dbus.dhcp6c: @@received command: CMD_START
Dec 11 15:27:09 (none) daemon.info arc_monitor: excute action:monitor_dhcp6c
Dec 11 15:27:09 (none) daemon.info arc_monitor: process radvd: IPv6 settings is not ready!
Dec 11 15:27:08 (none) daemon.info arc_monitor: process dhcp6d: IPv6 settings is not ready!
Dec 11 15:27:08 (none) daemon.info arc_monitor: Process escaped last time, set action:monitor_dhcp6c to restart
Dec 11 15:27:08 (none) daemon.info arc_monitor: Process dhclient6 is not found!
Dec 11 15:26:42 (none) daemon.info dhclient: bound to 100.74.83.170 -- renewal in 57 seconds.
Dec 11 15:26:42 (none) daemon.info dhclient: [bind_lease:1581] dhclient bind lease.
Dec 11 15:26:39 (none) daemon.info dhclient: [gratuitous_arp:125] dhclient gratuitous arp.
Dec 11 15:26:39 (none) daemon.info dhclient: [dhcpack:1394] dhclient receive ack from server(100.74.83.169).
Dec 11 15:26:39 (none) daemon.info dhclient: DHCPACK from 100.74.83.169
Dec 11 15:26:39 (none) daemon.info dhclient: [send_request:2730] dhclient send request.
Dec 11 15:26:39 (none) daemon.info dhclient: adapter index 6
Dec 11 15:26:39 (none) daemon.info dhclient: adapter index 6
Dec 11 15:26:39 (none) daemon.info dhclient: DHCPREQUEST on eth0.2 to 100.74.83.169 port 67
Dec 11 15:26:08 (none) user.debug syslog: command_handler(607):There is not WAN to be specified, use wan_dft_idx 0.
Dec 11 15:26:08 (none) user.debug syslog: command_handler(566):arca.dbus.dhcp6c: @@received command: CMD_START
Dec 11 15:26:08 (none) daemon.info arc_monitor: excute action:monitor_dhcp6c
Dec 11 15:26:08 (none) daemon.info arc_monitor: process radvd: IPv6 settings is not ready!
Dec 11 15:26:08 (none) daemon.info arc_monitor: process dhcp6d: IPv6 settings is not ready!
Dec 11 15:26:08 (none) daemon.info arc_monitor: Process escaped last time, set action:monitor_dhcp6c to restart
Dec 11 15:26:08 (none) daemon.info arc_monitor: Process dhclient6 is not found!
Dec 11 15:25:42 (none) daemon.info dhclient: bound to 100.74.83.170 -- renewal in 57 seconds.
Dec 11 15:25:42 (none) daemon.info dhclient: [bind_lease:1581] dhclient bind lease.
Dec 11 15:25:39 (none) daemon.info dhclient: [gratuitous_arp:125] dhclient gratuitous arp.
Dec 11 15:25:39 (none) daemon.info dhclient: [dhcpack:1394] dhclient receive ack from server(100.74.83.169).
Dec 11 15:25:39 (none) daemon.info dhclient: DHCPACK from 100.74.83.169
Dec 11 15:25:39 (none) daemon.info dhclient: [send_request:2730] dhclient send request.
Dec 11 15:25:39 (none) daemon.info dhclient: adapter index 6
Dec 11 15:25:39 (none) daemon.info dhclient: adapter index 6
Dec 11 15:25:39 (none) daemon.info dhclient: DHCPREQUEST on eth0.2 to 100.74.83.169 port 67
Dec 11 15:25:08 (none) user.debug syslog: command_handler(607):There is not WAN to be specified, use wan_dft_idx 0.
Dec 11 15:25:08 (none) user.debug syslog: command_handler(566):arca.dbus.dhcp6c: @@received command: CMD_START
Dec 11 15:25:08 (none) daemon.info arc_monitor: excute action:monitor_dhcp6c
Dec 11 15:25:08 (none) daemon.info arc_monitor: process radvd: IPv6 settings is not ready!
Dec 11 15:25:08 (none) daemon.info arc_monitor: process dhcp6d: IPv6 settings is not ready!
Dec 11 15:25:08 (none) daemon.info arc_monitor: Process escaped last time, set action:monitor_dhcp6c to restart
Dec 11 15:25:08 (none) daemon.info arc_monitor: Process dhclient6 is not found!

tracerrx
Sophomore

Re: Remote Desktop Connection error with HT2000W

@C0RR0SIVE if you get a chance to test again, next time perform a traceroute or MTR from the server back to the ip of the connecting client.  What @pswired and I have seen is that it will hit the hughesnetwork and die (assuming they dont know which modem has that IP).  This is almost definately a NAT issue (taking to long to register addresses they have handed out).  It seems to self-resolve after a couple minutes, but by then the RDP session has timed out.

 

 

C0RR0SIVE
Associate Professor

Re: Remote Desktop Connection error with HT2000W

Hrm, from what I remember because of CGN it wil drop out at some point in the Hughes infrastructure (unless testing back to my SME account...), so not sure that it would provide any real insight to run it from server back to the client.

That aside, I am testing right now, kinda have my hands full keeping an eye on everything as I am testing from multiple terminals...  My theory is... My SME account wont drop, ever, but my residential will.

@tracerrx, when you get a chance to test again, clear your HT2000w router side logs, set them for debugging, and see if you get the same error when an RDP session fails?  Gotta be quick, that log can fill up VERY fast... Or send logs to a syslog server?

tracerrx
Sophomore

Re: Remote Desktop Connection error with HT2000W

Sorry... Meant to traceroute or MTR the ipv6 (not ipv4) of the client.... since it's the only thing visible to us outside of the CGN.  However it should be proof enough that it's dying somewhere within the CGN.