cannot access samba shares from Windows server 2003

[clancyfan]

Hello,

Running a network of about 20 workstations, a windows 2000 server and a windows server 2003 + new fedora core 3 server.

All computers can access the samba shares except one. The 2003 server. I receive the error: The request is not supported when I attempt to access the samba server from 2003 server. I've tried from the command line (net use) and from network places, same error.

Any ideas?

 

[PHV]

And what are saying the samba logs ?

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244

 

[clancyfan]

The logs don't appear to be saying anything. I'm looking at the samba.log file as well as the specific log for the IP address of the 2003 server, it contains nothing.

I'm not a Linux expert so it's entirely possible I'm not looking in the right places.


Thanks for your help

 

[clancyfan]

Update:

I cannot access the Samba server with XP Pro machines either. XP Home however is okay.

Must be some Microsoft security issue.

 

[motoslide]

On the 2003 server, check the following entry:

Local Security Policies:
Local Policies --> Security Options.
Network Security: LAN Manager Authentication Level

Try setting to "Send LM and NTLM responses"

Do so at your own discretion, of course.

 

[clancyfan]

I may in fact give that a try. I have figured a workaround however. I am able to access the fedora server if I set Samba to user level security instead of password security. But this doesn't help my cause I am trying to create a single password login for all users.

The workaround is okay for now because I have 2 W2K servers that I use to set profiles and home directories on the fedora server, but the w2k3 server does not allow me to do this because it says the location is inaccessible. I'm referring to creating new users in active directory users and computers control panel.


Thanks,
Dylan

 

[clancyfan]

In my comment above I mean user level security in the samba file instead of server for a password server, which I am using my W2K server for.

 

[clancyfan]

Okay motoslide I tried your recommendation and indeed it has helped. I am now able to get a username and password prompt from on the W2k3 server machine when accessing the fedora box via \\servername\sharename. However it will not accept the credentials I provide. If I create a local user on the fedora server and create a local password (instead of relying on the password server configured in smb.conf) I'm sure it will work.

The most important aspect is working though, which is allowing me to create the profile path and home directory paths on from the W2k3 server. This is what I needed to accomplish so when the day comes to move all servers to 2k3, I am still able to create the user directories and profile paths from the 2k3 server.

Thanks for the help!

 

[clancyfan]

UPDATE:

Everything works great as long as the Server 2003 box is not listed as the password server in smb.conf. If a 2000 server is the password server, the 2003 server can access the Linux shares no problem. This is after making the changes recommended by motoslide above.

Anyone have any ideas why this would happen?

 

[motoslide]

The other Local Security Settings you *might* want to change deal with digitally signing communications:

Microsoft Network Client: Digitally sign communications
Microsfot Network Server: Digitally sign communications
(there are a total of 4 entries).
If you disable these, your password authentication may work. If you mess this up, Active Directory will fail and that isn't a pretty sight. Active Directory uses both the Client and Server entries for internal communications. Make sure you don't create a circumstance where one cannot talk with the other. Been there,.. Done that.. Spent a LOT of time on the phone...

 

[clancyfan]

Thanks motoslide but it isn't that important. It is unlikely I"ll actually need to access the user directories from the servers anyway. I just need to be able to set the path to the Linux box in the user profiles, which I can do, thanks to your tip.


Cheers,
Dylan