still no fix?

Started by Vern Faulkner, April 15, 2016, 08:51:19 PM

Previous topic - Next topic

Vern Faulkner

It's been five months and my Classic still cant report to MM2. It was working fine under MM1, even using the sattellite internet we have out here, so either th MM2 software or the classic software upgrade is the culprit.

Westbranch

Maybe not , the culprit may be NATting...  I asked if Xplornet used any kind of 'compression' and they told me , yes , and there are 2 types, one IP based and the other Web based...just like HughesNet in the US... I have a Hughes 1100 Modem, that sparked some head scratching...

then there is double NATting....http://www.practicallynetworked.com/networking/fixing_double_nat.htm....  I will be digging into the WiFi and modem when on site to see what I can find.... so far I have been using WireShark to intercept Classic comms with 159.201.65.203 (MM2).   the one thing I did find with a MS TraceRT was very long times for connections/hops from IP to IP address... 

you might try that...

I am in the same boat as you going fromMM1 to MM2 has been a head banger for me...  started last Nov when I upgraded to a 20xx version...

Andrew/Atop is working on a fix for some of the identified issues
KID FW1811 560W >C&D 24V 900Ah AGM
CL150 29032 FW V.2126-NW2097-GP2133 175A E-Panel WBjr, 3Px4s 140W > 24V 900Ah AGM,
2 Cisco WRT54GL i/c DD-WRT Rtr, NetGr DS104Hub
Cotek ST1500 Inv  want a 24V  ROSIE Inverter
OmniCharge3024  Eu1/2/3000iGens
West Chilcotin 1680+W to come