2003 share problem

[999Dom999]

I have a new G4 Powerbook running Panther 10.3.4 that can't access shares on our windows 2003 DC.

Our G5 desktops can view all the shares on this server and both the powerbook and desktops can view shares on all our other windows 2003 member servers.

Its Just the windows DC the Powerbook can't access, if I browse through Network then click the server and use the correct AD account I get the message The alias "servername" could not be opened, because the original item cannot be found.

I am running appletalk on the dc for the older macs. If I choose connect to server and add in the ip address it will allow me to to connect to mac volumes on the server but doesn't list all the shares on the server like the other G5's do.

Thanks for any help

 

[999Dom999]

Ok solved it. Dunno why but it was something I just remembered, the G5's seemed to use "guest" as a log in name without a password then all the shares popped up. If anyone knows why this is please let me know.

 

[jimoblak]

If all your shares appear with 'Guest' then you have a really unsecure network.

- - picklefish - -
Why is everyone in this forum responding to me as picklefish?

 

[999Dom999]

Well I'm a little confused why the administrator account will not allow access when the guest account will. I thought that this guest account must be a default mac account?

 

[jimoblak]

Check your Keychain application in Applications/Utilities... you may have an incorrect stored password set up and this is why the admin account fails.

- - picklefish - -
Why is everyone in this forum responding to me as picklefish?

 

[999Dom999]

Nope I can't login using any accounts. Now that guest is disabled that chucks out all the macs. I wasn't aware it was enabled, just taken over this network in my defense

Anyway I guess this must be some sort of authentication issue

 

[999Dom999]

OK at last I have found the solution from much searching on the internet:

Windows 2003's security policy encrypts all SMB traffic.

On the Server, open Registry, go to HKey_Local_Machine / System / CurrentControlSet / Services / LanManServer / Parameter / RequireSecuritySignature

set to 0

One note: If this is a domain controller, you will need to set it with the 'Domain Controller Security Policy' editor under the 'Administrative Tools' Menu. Otherwise it'll be reset nightly.

You need to go to 'Security Settings', 'Local Policies', 'Security Options'. You then need to set the 'Microsoft network server: Digitally sign communications' to disabled. It is enabled by default.

This info was found in this forum:

http://www.macosxhints.com/article.php?story=20030922153448490

 

[UNIX72]

The problem is within apple's UAM client.. Windows 2003 server by default prefers client/server two way authenication to be encrypted while apple sends plain unencrypted passwords. Simply upgraded your UAM

http://www.microsoft.com/mac/otherproducts/otherproducts.aspx?pid=windows2000sfm