"machine is not accessible" - how to fix???

John Harper harper at banks.scar.utoronto.ca
Thu Apr 9 17:14:49 GMT 1998


I've broken something on my NT box - when I try to connect to my Samba
server through the nethood I get an error popup that says:
"<servername> is not accessible
The storage control blocks were destroyed"

I can connect to another samba server with no problem, other users
from other machines can connect to the above server with no problem
either. I can connect with net use directly as well. I can't connect
from my NT client using any local account through the nethood.

After the failure, a net use shows 2 IPC$ connections, one with the
machine name all in caps, the other with only the first letter capped. A
similar connection to a "working" server only shows 1 IPC$ connection,
with first letter capped.

I think the problem began when I was playing around with the NT-DOMAIN
support (and had it working); then I moved the PDC to another samba
server. When connecting to that server I got messages about roaming
profiles being out of date etc (I did not configure it to do that, so I
thought). It tried writing updates somewhere....

I completetly reinstalled Samba on the problem server - I am forced to
conclude the problem lies on my client. I'm guessing something about
user profiles, but I can't see anything obvious.

So... can anyone suggest what might be wrong and how I can fix it?


John Harper
Academic Computing Coordinator
University of Toronto at Scarborough
harper at scar.utoronto.ca

More information about the samba mailing list