At work we are using the Nortel Extranet 3.x and 4.x client on Win 2k workstations.
Is there a way to *force* the workstation to log into an NT domain when the Extranet client starts its connection process. IE - the user gets a Username, Password, and Domain logon box when the VPN initiates its connection?
To hopefully make a long story short, VPN users need to change their domain password when logged in on the VPN... sometimes it works, but most times it doesn't. Our users are logged in via dial up. Logging shows that they do "talk" to the domain controllers to "log in" but as far as the DCs are concerned the workstations are NOT logged into the domain.
The Extranet client is installed as an application, not a service. TCP/IP and other related network configuration don't seem to be the issue... name resolution etc. function normally. We are using RADIUS.
I hope I've given enough info...
Bill Dunlap
Is there a way to *force* the workstation to log into an NT domain when the Extranet client starts its connection process. IE - the user gets a Username, Password, and Domain logon box when the VPN initiates its connection?
To hopefully make a long story short, VPN users need to change their domain password when logged in on the VPN... sometimes it works, but most times it doesn't. Our users are logged in via dial up. Logging shows that they do "talk" to the domain controllers to "log in" but as far as the DCs are concerned the workstations are NOT logged into the domain.
The Extranet client is installed as an application, not a service. TCP/IP and other related network configuration don't seem to be the issue... name resolution etc. function normally. We are using RADIUS.
I hope I've given enough info...
Bill Dunlap