VPN Client and DNS settings

Question

Hello,
here are few posts (quite some time ago) telling the same trouble:
The VPN Client does *NOT* restore the original DNS settings.
Upon BM3.8.2 Massimo told, that this is a bug in that version of the VPN
client. I face this issue with 3.8.16 and nwclient 4.91.4 with or without
the three currently available hotfixes [1]
Anybody else facing this trouble with the current VPN client release?
May be an older one works better, any experiences?
This trouble is fact even after clean disconnects. But it happens only now and then,
I might need to try it 50 times to see it once.
a followup in CMD boxes with ipconfig /all does show, that the times
to restore the original DNS settings vary from 2 to 30 seconds. Mostly about 5 seconds.
Massimo also told, that a "VPN-down" due to a Win-Shutdown can cause this: So is
there a possibility to trigger a "clean-VPN down" in the Win-shutdown sequence?
As a workaround I packed this line into all users "run" key:
netsh int ip set dns name="LAN-Verbindung" source=dhcp
so at least after a reboot it's corrected.
Any suggestions appreciated,
[1]
Novell Client 4.91 Post-SP2/3/4 NWSPOOL.DLL
Novell Client post-4.91 SP4 LGNCXW32.DLL
Novell Client 4.91 Post-SP4 NWGINA.DLL 1
IT-Beratung Rudolf Thilo
Schweinfurter Str. 131
97464 Niederwerrn
t: +49 (0)9721/6464840
f: +49 (0)9721/6464841
m: +49(0)171/685 9 685

Answer 1

Hello Craig,
thanks for your answer.
[VPN Client sometimes doesn't restore DNS settings after disconnecting]
e.g. TID 10096552 is telling such a trouble, that should be fixed with
BM VPN Client 3.8.10
> > Any suggestions appreciated,
> >
> This one seems to be so related to the design of the VPN client that
> you may need to open an incident to get it fixed, if that even would
> help.
>
> There used to be a utility designed to clean up after the VPN client,
> but I can't remember now what it was. I never tried it that I can
> remember.
Anybody else who knows about that tool?
After doing some "teachment" to these VPN users the incidents of this
trouble didn't show up as frequent as before. So I assume, that one
reason might be this:
Scenario
VPN connect
PCA connect to host in corporate LAN
PCA full screen *SHOULD* be activated (ALT+ENTER)
working, working, working
shutdown PC in corporate LAN
close VPN tunnel
shutdown local home office PC.
When it was missed to activate PCA fullscreen without noticing this,
then the "remote" start button is not visible.
So instead of shutting down the remote PC, the local PC is shut down.
By that, the local shutdown is killing (not cleanly disconnecting)
the VPN client. When this happened (and I 100% can reproduce this)
after the next boot of the home office PC the VPN connect will *ALWAYS*
fail. After another reboot the VPN connect will succeed again without
any problems.
Is this a known issue? (I cannot find that TID I found before telling
missbehaviour when VPN connects are not disconnected clean. IIRC this
was something fixed in a VPN client version /several/ subversions ago)
Home Office PC = XPSP2+Hotfixes, VPN Client BM 3.8.16, nici from that
one first, now taken from NWClient 4.91.4, no difference.
Regards, Rudi.
IT-Beratung Rudolf Thilo
Schweinfurter Str. 131
97464 Niederwerrn
t: +49 (0)9721/6464840
f: +49 (0)9721/6464841
m: +49(0)171/685 9 685