SecuRemote Breaks NT RAS

[roadrunner]

SecuRemote Breaks NT RAS
Once SecuRemote is installed, things seem to work. That is: remove network card from notebook, boot, connect via RAS to ISP, use VPN to connect to home site. However, if I change anything within the network settings, RAS no longer works. If I deinstall SecuRemote, reinstall RAS on the client, remote access still does not work. How can I fix this?

Scott McMeek offers this advice:

I had this problem with the version you are using and the solution was to install TCP/IP stack as normal, then RAS and all associated patches, then securemote. After I installed securemote the TCP/IP stack worked, but I couldn't contact the PDC for my domain - as it turned out, DHCP had stopped working because the securemote stuff was being bound to the adapters before the DHCP stuff, so DHCP was failing. What I did was go into the network control applet and change the binding order on all the devices except RAS to have the NIC card bind first, THEN the dialup adapter on all BUT the RAS service, which of course you would make bind the NDIS WAN wrapper for the modem (and securemote) first, then your NIC card.

What I did find however, if like me you have a modem, a token ring card AND an ethernet card in your laptop, then you need [SecuRemote build 41xx] anyway - two NICs just doesn't seem to work, even if you change the order of the binding.

-- PhoneBoy - 05 Apr 2004


FAQForm
FAQs.Class: SecureClientFAQs
FAQs.OS:
FAQs.Version: