Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Resolve Windows server connection issues via UAM' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Resolve Windows server connection issues via UAM
Authored by: kidventus on Sep 16, '04 06:48:22AM

People People People...

This happened all the time on my Samba shares on my Linux box and Windows 2000 / XP boxes. Basically, you're looking for a complicated solution to a simple problem. Mac OSX almost always with very little change to the server (sometimes just a reboot) refuses to authenticate because the challege is wrong and it won't let you pass right through with the old creditials. The non-root-canal way of handling this is going in to your keychain and deleting the offending entries... then simply retry to connect and you'll be prompted for a username / password again.

The only reason it doesn't prompt you now is because you have the login in your keychain.

Woozers.. deleting the whole preference directory?



[ Reply to This | # ]
Resolve Windows server connection issues via UAM
Authored by: johram on Sep 16, '04 08:03:30AM

I can never connect to smb shares by browsing.

i have no idea what UAM is...
but the only way i can connect to my windows shares is by typing out the full path in the "connect to" pane.

as in

smb://MSHOME@WEBSERVER/LANUPLOAD

i clear out the username and password field and tick the "save to keychain" option. i never get prompted for passwords again (when using connect to pane). note that mounting via browsing smb shares remains fruitless.

would this help anyone?
maybe.
probably off topic anyways.
later,
johnny

---
-
Send your windows friends over to http://osswin.sourceforge.net/
Read http://www.groklaw.net/



[ Reply to This | # ]
Resolve Windows server connection issues via UAM
Authored by: kuwan on Sep 17, '04 01:33:24PM
The non-root-canal way of handling this is going in to your keychain and deleting the offending entries... then simply retry to connect and you'll be prompted for a username / password again. The only reason it doesn't prompt you now is because you have the login in your keychain.
I, and others with this specific problem, had tried this already and it didn't work. If you actually google for the phrase "Could not connect to the server because the name or password is not correct" then you'll find a lot of frustrated users that have tried everything (including deleting keychain entries) but found no solution.

[ Reply to This | # ]