My guess is that this is related to the hoops that you have to jump through to get a Win7 system to talk to a Samba domain. If you're on CentOS, you're likely running Samba 3.0.33, which is incompatible. Samba3x is now in the CentOS base repos, but there are some hoops that you have to jump through to upgrade (namely moving your .tdb files to their new home in /var/lib/samba from their default /var/cache/samba location).
The upgrade can't be done directly (e.g. yum update) because of the different naming convention. So to upgrade you'll need to do a rpm -e `rpm -qa | grep samba`, then a yum install samba3x. Good luck! R Rubin Bennett rbTechnologies, LLC 1970 VT Route 14 South East Montpelier, VT 05651 (802)223-4448 x101 http://thatitguy.com "I cannot believe that the purpose of life is to be happy. I think the purpose of life is to be useful, to be responsible, to be compassionate. It is, above all to matter, to count, to stand for something, to have made some difference that you lived at all." Leo Rosten 1908-1997 -----Original Message----- From: Christian Campbell [mailto:[email protected]] Sent: Wednesday, April 13, 2011 2:02 PM To: [email protected] Subject: Re: Server 2003 SP1 broke connection to SAMBA Apologies... I'm at SP2. Also changed LAN Manager authentication to "Send LM & NTLM responses" with no change. -----Original Message----- From: Vermont Area Group of Unix Enthusiasts [mailto:[email protected]] On Behalf Of Evan Flynn Sent: Wednesday, April 13, 2011 1:59 PM To: [email protected] Subject: Re: Server 2003 SP1 broke connection to SAMBA Not sure on that one, but SP2 for Win2k3 is the latest version, and it's been out since 2007. On Wed, Apr 13, 2011 at 1:49 PM, Christian Campbell <[email protected]> wrote: > Fellow enthusiasts, > > > > I've got a Windows 2003 server that just got updated to SP1 (Don't ask). > SP1 broke our ability to connect to a SAMBA share on a RHEL server via > UNC path with the following error: No network provider accepted the > given network path. I disabled encrypt third party SMB as well as > disabling digitally signing communications on the Win(bl|d)ows server. > > > > Would anyone happen to know what security settings I need to relax on > our > W2K3 box to restore our ability to connect to our SAMBA share? A .5 > hour on Google didnt produce much else. > > > > Thanks in advance. > > > > Regards, > > Christian > > > > Christian Campbell > > Systems Engineer > > > > Bruegger's Enterprises Inc. > > Desk: 802-652-9270 > > Cell: 802-734-5023 > > Fax: 802-660-4034 > > Email: ccampbell at brueggers dot com > > > > PGP Public Key available via PGP keyservers or > > http://www2.brueggers.com/pgp/ccampbell.html > > > > "Computer Science is no more about computers > > than astronomy is about telescopes." > > --E. Dijkstra > > > >
