Good advice has already been given, however, in order to determine if therexe2x80x99s a specific share causing the issue, Ixe2x80x99d suggest two things:
1) Create a new blank user, connect from there and try to see if this new user exhibits the same problem/behavior.
2) Additionally, disconnect all shares and start connecting one by one and perform the voodoo magic to reproduce the xe2x80x9cdisconnectxe2x80x9d dialog (with each individual connection). That way you could see if the problem only manifests in some connections but not others, or all.
Do you have any server log or anything that could be an indication of a process hanging or waiting for a server response that never comes? (already suggested)
UPDATE: Today I made a test. I connected my 10.6.4 to a Samba box running an ancient version of Fedora (probably 3-4 years old). And when I had the connection open, I halted the server to get the Server connections interrupted dialog:
Herexe2x80x99s how my dialog looked like:
public is the name of the share and nippur is the name of the server.
Now thatxe2x80x99s why your dialog looked weird. Are you sure youxe2x80x99re running 10.6.x?
UPDATE 2: Youxe2x80x99re running 10.6.4 but using ADMitMac, which "turns a Mac into a true Active Directory clientxe2x80x9d. I suspect thatxe2x80x99s where the problem lies. Ixe2x80x99d disable or remove that and start from there. Ixe2x80x99m 99% sure that without it, the problem will go away. The problem will then turn onto a new questionxe2x80xa6 why? But thatxe2x80x99s an entire new world and only Console Logs will help (plus, of course, ADMicMacxe2x80x99s tech support).