Ouch Posted May 3, 2006 Share Posted May 3, 2006 OK so i recently set up a new active directory domain to repace and old one and everything is running fine with the windows clients but i am having difficulty getting my macbook to connect to the shares on the new server using SMB. When i try and mount a network share for example smb://sqdc01.sqnet.local/home i get the error "could not connect to server because the name or password is not correct." The problem is the pasword prompt is never displayed so i can't enter my new account information and i can't see the server when i browse the network in finder - but i can see other windows clients and authenticate to them (the password box is displayed) I figured it was a cached password problem so erased all appropriate references from keychain and tried again - no luck. Then i figured the .GlobalPreferences.plist could be corrupt so i recreated that but still no luck. The new server is running ISA2004, which wasn't the case with the old one (but there is a firewall rule which permits all traffic to and from the internal network to the server so this shouldn't be an issue) Link to comment Share on other sites More sharing options...
Ouch Posted May 6, 2006 Author Share Posted May 6, 2006 My one and only bump. (I remembered i had to change the SMB signing policy on the server but that hasn't solved the problem.) Link to comment Share on other sites More sharing options...
Fravin Posted May 7, 2006 Share Posted May 7, 2006 Welcome to the club.... Link to comment Share on other sites More sharing options...
Ouch Posted May 7, 2006 Author Share Posted May 7, 2006 Are you using SBS or do you have ISA installed on the same box? Link to comment Share on other sites More sharing options...
etx Posted May 10, 2006 Share Posted May 10, 2006 I don't have a real answer for you, But over the years I've noticed the Samba implementation on OSX is a complete disaster. Apple actually enabled an option that would slow down the transfer speed between a 32bit windows box. Coincidence? I doubt it. Link to comment Share on other sites More sharing options...
kristie_jeff Posted May 10, 2006 Share Posted May 10, 2006 I don't know if this will fix the issue you are having, but when I had an issue connecting to windows shares from osx, I had to do the following: make a new file called nsmb.conf in /etc edit that file so that it reads [default] minauth=0 save it and restart Before, when I tried to connect to server, it would just give me an error 50, but never ask for authentication. Now it asks for the password and will even accept blank passwords. Jeff Link to comment Share on other sites More sharing options...
Ouch Posted May 10, 2006 Author Share Posted May 10, 2006 Thanks for the suggestion but it didn't have any effect - this is really annoying, i could connect to the old server fine - i'm beginning to think it must be something to do with the server configuration but who knows what! Link to comment Share on other sites More sharing options...
leoniloilo Posted May 11, 2006 Share Posted May 11, 2006 hello... see my post at http://forum.osx86project.org/index.php?showtopic=15897 hope it helps Link to comment Share on other sites More sharing options...
Ouch Posted May 11, 2006 Author Share Posted May 11, 2006 I thinks it's more than just the signing policy - which is configured as required. It can't be anything on the mac either cause it can access shares on XP clients. Link to comment Share on other sites More sharing options...
Ouch Posted May 16, 2006 Author Share Posted May 16, 2006 Definitely not a problem with the mac, I just had to completely re-install Mac OS cause SU 2006-003 hosed my system and i still can't connect to server shares. Link to comment Share on other sites More sharing options...
cdfs Posted May 19, 2006 Share Posted May 19, 2006 Try it with smb://username@servername/sharename I'm working here in a 2003-AD. The only problem I have is with DFS-Shares, but I can ship around that by mounting from the original servers. CDFS Link to comment Share on other sites More sharing options...
Ouch Posted May 19, 2006 Author Share Posted May 19, 2006 No go unfortunately. I have done some further trials, building an new server and installing ISA on it didn't reproduce the issue so i'm thinking i can eliminate ISA from the list of probable causes. At first i thought perhaps Netbios over TCP/IP was the problem but using the IP address instead of servername presents the same problem. Using mount_smbfs from the command prompt gives the same error as displayed in the console when using the GUI method: mount_smbfs: negotiate phase failed: syserr = Connection refused however using smbclient from the terminal i can access and browse the share - which seems very odd! I can also mount_smbfs to shares on other machines. This is a real pain. Link to comment Share on other sites More sharing options...
djn11 Posted May 20, 2006 Share Posted May 20, 2006 Check out Admitmac from Thursby. We have been using it for a while in an Active Directory 2003 environment. They currently have a beta fro Intel OS X machines. Link to comment Share on other sites More sharing options...
Ouch Posted May 20, 2006 Author Share Posted May 20, 2006 I've been aware of admitmac prior to Mac OS including AD support - i don't really want the mac joined to the domain, i just want to access shares on the domain controller which should be possible without paying for admit mac. Link to comment Share on other sites More sharing options...
hairyneanderthal Posted May 22, 2006 Share Posted May 22, 2006 I had to do the following reduction of security on my 2003 AD Domain controller before OSX would connect to SMB shares. Accessing a Windows 2003 Share from OSX I've been aware of admitmac prior to Mac OS including AD support - i don't really want the mac joined to the domain, i just want to access shares on the domain controller which should be possible without paying for admit mac. Link to comment Share on other sites More sharing options...
Ouch Posted May 22, 2006 Author Share Posted May 22, 2006 SMB Signing policy is as it should be. Link to comment Share on other sites More sharing options...
hairyneanderthal Posted May 22, 2006 Share Posted May 22, 2006 Ah.. okay. I guess that's what you meant by Post #2 SMB Signing policy is as it should be. Link to comment Share on other sites More sharing options...
Recommended Posts