win2k3 host will not connect to samba share-linux

[f0rmat]

I have multiple windows 2003 boxes that I can not connect to a samba share. I can connect to the same shares using windows 2000, and the windows 2003 box can connect to a share on windows xp(all using net use and net view) I cannot however do a net view \\linuxserver
I get a "System error 50 has occured, The request is not supported."

The problem appears to be within windows 2003 since my XP machine can do a net view \\linuxserver without a problem, however when I do a net view \\linuxserver on windows 2003 I get the error above.

Any ideas? I'd be most appreciative.

 

[Roadki11]

Thought that was problem with older versions(2 and older) of samba, you using the newest version(3+) of samba?

RoadKi11

 

[f0rmat]

I believe its version 3. I've seen postings of it happening with older versions but since this is only happening with windows 2003 and not at all with windows 2000 or windows xp I have a feeling it has something more to do with the windows side of things. It wouldn't make sense for only w2k3 not to work if it was a samba config, I'd expect none of the m$ to work.

 

[f0rmat]

some more info on this. Both nmbd and smbd are running. Samba version is [root@buildlog samba]# smbd -V
Version 3.0.10-1.4E.2

and I believe it's an actual issue with this particular linux box hosting samba. From my two win2k3 boxes I can do a net view \\maven and get a perfectly fine response, but when I do a net view \\buildlog it craps out. So oddly, this behaviour is specific to windows 2003 and buildlog... only. Windows 2000 and Windows XP work fine on either machine

 

[TheLad]

Could this be an issue with Keberos logins? TBH I don't know that much about it but I remember a similar problem with commectivity issues to a W2K3 server being resolved by enabling Keberos on a Samba server... (I also remember the same issue occuring with an XP SP2 desktop build as well)

--------------------------------------
"Insert funny comment in here!"
--------------------------------------

 

[f0rmat]

It had to do with the share level I was sharing it out at on the samba config. security = server was giving a error, but security = share did not, and made it work fine.

I assume I could've gotten it to work with security = server, but this machine isn't really that confidential, so I wasn't going to bother.