We have a Cisco PIX 506e firewall, and I have set it up so that users can use the Cisco VPN client (ver 4.8) to make a VPN connection to the firewall and access the internal network. It works fine for most people, yet for one user (my boss!), whenever he connects to the VPN, and then connects to the office LAN, his connection gets dropped intermittently. It is only noticeable when he is using our client-server ERP program (Axapta) - the program says it cannot find a certain file, and Axapta support said it was a network issue.
This first happened a few weeks ago, when we tested out the VPN at the office through a dial-up connection. Then he put his laptop back in the docking station, and the Axapta error started occurring; the only way I could fix it was to completely uninstall the network card drivers, TCP/IP, run a registry cleaner, and then reinstall everything (I did more than that, yet that seemed to be what worked). However, I did not uninstall the VPN client software (ver4.0.1), and everything was fine.
I then wrote some batch files, first one to connect the network drives after connecting to the VPN:
net use * /del /y
net time \\ITGFILESERV /set /y
net use g: \\itgcrm\goldmine
net use h: \\itgfileserv\acct$
net use i: \\itgfileserv\itg
net use j: \\itgfileserv\itec1
net use K: \\itgfileserv\nonwima
net use L: \\axapta\axapta
net use N: \\iomeganas\public1
net use o: \\itgfileserv\oi
net use p: \\itgfileserv\public
net use q: \\itgfileserv\quotes
net use s: \\itgfileserv\pos
net use t: \\itgfileserv\triprpt
net use u: \\itgfileserv\%username%$
net use w: \\itgfileserv\wima
net use X: \\itgfileserv\software
and another to clear all the network settings after disconnecting from the VPN:
net use * /del /y
net use /persistent:NO
ipconfig /flushdns
nbtstat -R
nbtstat -RR
ipconfig /renew
I thought installing the newer version of the Cisco VPN client (ver 4.8) and using the batch files would help, yet as soon as I installed the new client (not even trying the VPN connection), the Axapta errors started again. He was able to see all the network drives, use Outlook to connect to our Exchange server, yet still this recurring error in Axapta.
This time I had to do all the repair steps I did before, in addition to un-installing the VPN client and going through the registry to remove all traces of it.
Maybe the docking station has something to do with it? Or maybe the VPN client locks up some ports that Axapta needs? Any suggestions would be most helpful.
Thanks,
Ross
Start Free Trial
