caimbo

We seem to be getting more people coming back from holidays or extended periods with their laptops to find that the drives wont map properly. But the mappings work for everyone else. They worked fine before their holidays. In the first case above the user can log on to the drives on another PC with his network profile, just cant do it on his own whereas I or any other network user could map the drives on his machine. This makes me think its not DNS related

Can you tell me how to configure the logon script to output to a log

when user logs on, one particular drive will not map from the logon script I can map it by IP in "my computer" but not by name. If I log on to his machine the script maps the drive perfectly. In addition if he logs on to another machine the drive maps perfectly wassup???

We have a customer coming to our site next week with his laptop He has a program on his laptop called Rhapsody. Ive been told that he has an active licence on his machine so it should just be a matter of letting him connect to the network I need to restrict his access to everything else on the network except for our server on which the licence server program Flexlm runs What would be the best way to restrict his access I have created an account on AD which makes him a domain user Since his computer has never been on our network before there will be no entry in AD for it Does this then mean that if he tries to make a UNC mapping to our licence server, it will ask him to authenticate and that will be all that is required?