I've tried to put all the info here so bear with me!!
We use a 3rd party solution to dial-up and get secure access to our networks. We have a fair amount of remote users with ISDN lines installed who connect to this service (W2K Pro).
All is fine when this is configured (with the ISDN TA attached - in this case a BT Ignition Pro A.K.A. Omninet Plus DSS 1). There is one change we have to make in the settings which is to change the modem protocol from AUTO (1Ch) to V120(64k).
However, once the laptop (Dell Latitude) is booted without the ISDN box attached it seems to lose these settings. The next time the user is at home and tries to connect the settings for the change of protocol have been lost with the result that users can't connect.
Users have full rights to the local machine and the problem only appears after they have booted the laptop away from the ISDN box. When we were previously using an NT4 RAS solution we never had this problem (although we never needed to change to protocol to connect).
Any ideas gratefully received!!
We use a 3rd party solution to dial-up and get secure access to our networks. We have a fair amount of remote users with ISDN lines installed who connect to this service (W2K Pro).
All is fine when this is configured (with the ISDN TA attached - in this case a BT Ignition Pro A.K.A. Omninet Plus DSS 1). There is one change we have to make in the settings which is to change the modem protocol from AUTO (1Ch) to V120(64k).
However, once the laptop (Dell Latitude) is booted without the ISDN box attached it seems to lose these settings. The next time the user is at home and tries to connect the settings for the change of protocol have been lost with the result that users can't connect.
Users have full rights to the local machine and the problem only appears after they have booted the laptop away from the ISDN box. When we were previously using an NT4 RAS solution we never had this problem (although we never needed to change to protocol to connect).
Any ideas gratefully received!!