I have student machines set to auto login and connect to a pair of network drives. once the drives are connected a program (successmaker if your interested) usually starts up right after and the students can then begin with their lessons.
the problem, when the machines boot straight into the user account i get an afp conection failed error with one of he network drives but not the other. but, when i log off and log back into the account both drives are connected and the program runs fine.
happens with any version of osx 10.2.8, 10.3.9, and 10.4.9/10.4.10. it's a strange thing.
it seems to me that the issue has to do with the machine not getting an IP right after startup, but when the user is logged off then logged on because an ip has already been defined there are no issues with connecting to the network drives.
has anyone else come across this issue? and more importantly, has anyone found a fix for this?
the problem, when the machines boot straight into the user account i get an afp conection failed error with one of he network drives but not the other. but, when i log off and log back into the account both drives are connected and the program runs fine.
happens with any version of osx 10.2.8, 10.3.9, and 10.4.9/10.4.10. it's a strange thing.
it seems to me that the issue has to do with the machine not getting an IP right after startup, but when the user is logged off then logged on because an ip has already been defined there are no issues with connecting to the network drives.
has anyone else come across this issue? and more importantly, has anyone found a fix for this?
