Unless you are using Win9x, inorder to log-on to a domain, the computer must be joined to the domain. A computer can only be joined to a single domain at a time. In order to log-on to a second (or third) domain, the computer must be removed from the first domain. Only an administrator (or someone given the specific user permission "join a computer to the domain") can join a computer to a domain. When a computer is removed from a domain, all record of that computer is also removed. Therefore, the entire process must be run again in order for that computer to later rejoin the domain.
Given all this (and the fact that NetSwitcher isn't an option), you really have 2 choices:
1. Create trust relationships between the 3 domains so thata mobile user can log-on from any location using the credentials from his home domain. Specific permissions which specify access rights will need to be enabled at those locations other the user's home station.
2. Don't join the notebooks to ANY domain. Configure them to use a generic workgroup. At all three locations, create a user account using the SAME user ID and password for each mobile user. On the mobile user's notebook, create a local account also using the same user ID and pasword. At each location, the mobile user will log-on using the local computer account. The domain will recognize these credentials as being valid and allow the user to map and access local resources. But, the user will not be able to browse the local network.
The only way I can think of to automate this would be to create batch files for each of the three locations for each user. Each batch file would consist of a series of NET USE commands that would connect the user to those local resourceshe needs access to. The user would still need to run the appropriate batch file after logging on to his local computer.