"Incomplete receive of encrypted data" error

[edmclen]

My boss's laptop is having difficulty connecting to the shares on the VPN. Everything worked fine several days ago, but now he is not able to access any folders once they are displayed onscreen. After looking through the log file, the debug option reveal the following error: "Incomplete receive of encrypted data." When he selects one of the shared folders, there is a long hourglass-pause, which is followed with an error about his computer not having access to the network drive.

I have disabled all firewalls other than the one native to Wingate and have disabled most of the Norton features and have now run out of ideas short of reinstallation. Any other ideas?

[jamesc]

The error message about the incomplete encrypted data will only show up in 2.0.4 as it's a new message that was added in response to a problem that we were having. According to the programmers it is entirely normal to see this and is not actually a problem, they will probably remove the entry for the next version.

From the sound of your Bosses PC symptoms, you may have a problem with the MTU of your connection. When you are connected into the host from the joiner, you can do a small test to establish your correct MTU (Maximum Transmission Unit).

If the WinGate Hosts' internal IP Address is 192.168.0.1, then from the joiner, do the following.

(Windows) Start Menu --> Run --> cmd

Code: Select all

ping -l 1500 -f 192.168.0.1

If you do not receive replys then lower the 1500 to say 1000

Code: Select all

ping -l 1000 -f 192.168.0.1

If you do not receive replys then lower the 1000 to say 600

Code: Select all

ping -l 600 -f 192.168.0.1

Once you start getting replys, edge the number up from 600 to say 800 etc etc... until you find your optimum setting. Once you have obtained it, download this utility: http://www.dslreports.com/drtcp

And if you have a dial up connection, you must place the MTU into the red box as shown in image below. Once done, restart your computer and try to use the files in the shares again.



You should test back from the host to the joiner too.