The problem is that when dialling in the users' login script is not run. The cause is almost certainly that a name/passwd dialog is not initiated on login (see workaround #2 below).
The laptops (WinME, Office 2000) are configured to logon to the network (NT4, SP6a) via Cat5e TCP/IP which works fine (Network properties identical to other working machines), and to dialup remotely, which is what will be used 99.9% of the time.....
A number of standard dialup connections have been established (tel#=# of the modems in the back of our server, all other config as default - all as per our other remote access machines).
When people logon to the network, a small batch file is run (see attached) which is specified by user in the login script dialog of NT User Manager/<user>/profile. These simply configure network drives individually for each user, and is used by remote and office workers. They work fine on the network, but not by people dialling in, this is a known and common problem which has two accepted work-arounds :
1) Specify to 'ghost' network connections, which then enables them as and when they are accessed. This does not always work in my experience, but I have tried it anyway.
2) When booting up, press cancel at the windows logon - since there is no server present it makes no difference whether or not you logon to windows or not. This forces windows to provide a name/passwd/domain dialog when logging on to the server for authentication, which in turn ensures the login scripts run.....at least is has on every other machine I've setup for remote access.
The users have been created as standard user accounts on NT, they all have Dial In permission set, and all accounts work properly from the laptop over a network connection, and from a desktop. File and Printer Sharing is enabled, the user has a local account on the laptop, and on the Server. We are utilising a standard NT Domain.
UPDATE : Having just tried to repeat the process, but with a check in the 'Log on to network' box of dialling properties, This forced the password dialog, to which I got the response "Cannot contact an NT domain to validate your password, etc..." although the Remote Access Manager confirmed that the connection is present. This would seem to be the root of the problem, but I cannot see what is different (especially server side) from other remote access scenarios. I have run through this method with my own user name (admin permissions) too, but no change.
I have also changed the modem speed (laptop) to 9600, to ruleout that possibility (a long shot admittedly) but to no avail.
Anyway - any suggestions would be gratefully received, as I am fast running out of ideas!
Jonathan Challis
IT Manager
Direct Line: 01353 645240
Mobile: 07776 020486
Fax: 01353 664369
The laptops (WinME, Office 2000) are configured to logon to the network (NT4, SP6a) via Cat5e TCP/IP which works fine (Network properties identical to other working machines), and to dialup remotely, which is what will be used 99.9% of the time.....
A number of standard dialup connections have been established (tel#=# of the modems in the back of our server, all other config as default - all as per our other remote access machines).
When people logon to the network, a small batch file is run (see attached) which is specified by user in the login script dialog of NT User Manager/<user>/profile. These simply configure network drives individually for each user, and is used by remote and office workers. They work fine on the network, but not by people dialling in, this is a known and common problem which has two accepted work-arounds :
1) Specify to 'ghost' network connections, which then enables them as and when they are accessed. This does not always work in my experience, but I have tried it anyway.
2) When booting up, press cancel at the windows logon - since there is no server present it makes no difference whether or not you logon to windows or not. This forces windows to provide a name/passwd/domain dialog when logging on to the server for authentication, which in turn ensures the login scripts run.....at least is has on every other machine I've setup for remote access.
The users have been created as standard user accounts on NT, they all have Dial In permission set, and all accounts work properly from the laptop over a network connection, and from a desktop. File and Printer Sharing is enabled, the user has a local account on the laptop, and on the Server. We are utilising a standard NT Domain.
UPDATE : Having just tried to repeat the process, but with a check in the 'Log on to network' box of dialling properties, This forced the password dialog, to which I got the response "Cannot contact an NT domain to validate your password, etc..." although the Remote Access Manager confirmed that the connection is present. This would seem to be the root of the problem, but I cannot see what is different (especially server side) from other remote access scenarios. I have run through this method with my own user name (admin permissions) too, but no change.
I have also changed the modem speed (laptop) to 9600, to ruleout that possibility (a long shot admittedly) but to no avail.
Anyway - any suggestions would be gratefully received, as I am fast running out of ideas!
Jonathan Challis
IT Manager
Direct Line: 01353 645240
Mobile: 07776 020486
Fax: 01353 664369