Discussion Locked

Roaming Profile Not Available....

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi all,

Can anyone answer me this? My org. is running NT 4.0 Srv and NT 4.0 clients(SP6), and utilising mandatory profiles. Over the last couple of days, some users can logon OK, others get "Your roaming profile is not available. You will be logged on with the locally stored profile(5). This can be on the same workstation, one logs on fine the other gets this message.

Thanks in advance, Stephen.....

7 replies

by erikdr

AFIK this is a hickup happening more frequently in larger domains, we also frequently have NTW complaining that there is a 'slow link' detected and then at least offering the option local-vs-network profile.
Probably you will have to do research inquite a number of tuning parameters. As far as I remember somewhere in the MS knowledgebase it is stated how long NTW logon waits while searching for the LAN profile, and how to increase this wait. Furthermore, LAN performance research (e.g. with tracert tooling) can then show some correlations between the errors and the present LAN load. Finally, how to increase the LAN throughput is the most complex story of all and forces you to firstly find the real bottleneck - cable, router, server NIC etc.

Hope this helps,

/ The Netherlands

by tony hogan

I've also had this problem in larger domains -and- with remote users. You can resolve this by adding LMHOST entries that will resolve the domain name directly.

In re: to the LMHOSTS file entries are:
x.x.x.x servername #PRE #DOM:domainname
x.x.x.x "domainname 0x1b" #DOM
NOTE - in the above quoted domain name it MUST! be fifteen characters between the first quote and the 0x1b - i.e. pad the domain name with spaces up to 15 characters -if you don't do this it does not work.

This should resolve the resolution issue.

-tony

by bill.parks

In addition to authentication troubleshooting, try these steps. First, identify if it the same users haveing the logon issue on no matter what machine they log onto. If JSMITH cannot log onto Machine A, B, or C, but JDOE can, then delete JSMTIH'S roaming profile and create it again. This leans towards file corruption or anything besides network connectivity. Since its mandatory, there is no important info you'll need to worry about losing. On the other hand, if JSMITH cannot log onto Machine A and B, but can log onto C, follow the suggestions from the replies above.

This discussion is closed to new replies.