Samba & Win2k Server
 

Windows 2000 Domain.

Client / Win2k Pro machines can see / access Samba

Server / Win2k Server machine can see / cannot access Samba, error (network path is not found).

WTF is the deal ?

disable your firewall

it doesnt HAVE a firewall,

setup command, firewall disabled.

iptables everything accept

no chains


Wouldn't you think that ALL the machines woulnd't be able to connect if it was a firewall ?

Don't get mad:rolleyes:

That was just to be sure that your linux box wasn't blocking the packets from that specific box......

Ok, lets start from the begining..... are you trying to access the netbios name or the IP?

Are you able to ping both computers?

Have you tried to map the drive? ( \\linuxbox\share)

Take it easy ;)

I've been at this for over a few hours, and its seriously starting to get to me.

Every kind of service works, EXCEPT samba to the Win2k Server

Pings ip work, netbios name ping works, ssh works, http works, https works, all backwards compat on netbios name.

share setup on share level.

I've looked all around the net, and i've never seen anyone trying to setup a Samba WITH a Win2k Server.

The Win2k Server isnt running any kind of packet filter / firewall.

(win2k Server)
Samba machine shows up in network neighborhood.
Cannot access samba from network neighborhood
Cannot access samba share via \\netbiosname
Cannot access samba share via \\netbiosname\share
Cannot access samba share via command: net use x: \\netbiosname\share
Cannot access samba share via windows: map drive x: \\netbiosname\share

(win2k pro)
Everything works 100%

you'd think that it'd work, but for some god forsaken reason the win2k server just cannot communicate with samba.
Its gettin really stupid really quick.

sounds like it could be a username problem. Try logging in with the username from the win2k pro box. This is just a shot in the dark. Good luck.

Hmmm,

In your smb.conf file there is a "workgroug = xxxxxx" command. Does the name of the workgroup correspond to the name of the Windows 2000 domain?

Are all the Windows 2000 professional machines members of the domain? That is, has a machine account been created on the Windows 2000 domain controller for each one?

If so, you may have to add the Samba machine to the Windows 2000 domain. Here are the instructions.

Create an account for your Samba machine using the Windows 2000 tools on the domain controller.

Go to the command line on the Samba machine and type:

smbpasswd -j domain_name. Substitute the name of your Windows 2000 domain for domain_name.

Let me know if it works.

nope dont work, already created a computer account for it.

The domain is in native mode. If it was a user name / passs, the box would come up :)

All machines are in the domain, the workgroup is the netbios name of the domain.

unfortunatly through everything I've read, I've never heard anyone actually attempting to get a Windows Server to access a Samba Server. Maybe theres an incompatibility problem with the software?

I don't understand. What doesn't work?

I currently have two Windows 2000 member servers as members of my Samba domain. One runs a MS SQL application that users who log onto the Samba domain use. The other is a being used temporarily as a RRAS dial in server running Windows 2000 terminal services.

I have set up Samba to be a member server on a Windows network before.

Let us see what you have overlooked. Is your Samba machine, a member of the Windows domain? If you work with me, we may be able to resolve the difficulty.

What version of Samba are you using?

I'm having the same problem, except...lol...he's farther along than I am. Could his problem with the file system itself?? NTFS vs. FAT?

Samba 2.27
On RedHat 9.0 rpm install

The problem is, the Win2k Server machine cannot access any shares off the Samba Server.

Cannot \\samba\share
Cannot \\ipofsamba\share

But every other computer in the domain can. But there are all Win2k Pro.

The Win2k Server is not running a firewall, is not running any filters. Just normal services. And to boot, every service OTHER than the Samba can be accessed from the Win2k Server to the Samba Server.
ex:
ssh
http
https
webmin

That command straight forward didn't work.

Had to use

smbpasswd -j domain -r dc -U administrator%password

Before I did that, I redeleted the Samba Server computer in the active directory, and using the command recreated it. Samba shares still aren't being able to be accessed from the Win2k Server

Strange...

Do you log on to the Professional machines with the same user name and password that you log on to the Server?

Samba 2.x emulates NT 4.0. You say your network is running in native mode. I assume you mean native mode as opposed to mixed mode.

Does native mode allow NT 4.0 machines to join the domain? I do not remember.

The samba server 'initally' was setup in just straight share mode, allowing even guest access.

Changing it into domain, forces the clients into the box message, user/pass.

Taking it out of domain back to share removes that. BUT.. the 2k Server either way, does not get any 'share' activity, no user/name just acts like the machine isn't even up and running.

And the domain IS in native mode, and joining the Samba to the domain worked. The computer account was created.

Why work for Pro but not Server edition?