I think it's probably a Master Browser problem. Google a bit on that and try changing your OS level in Samba up and down. Try joining the Samba mailing list if all else fails. There's a lot of guys on that list doing what you're attempting.

I checked the master browser, and it is the Win2k Machine.

Since its the DC i'd assume it'd have to continue to be the master browser?

Been a while sice I've messed w/ AD crap but yeah, I think you're right. Try searching here

can't seem to find out anything on it, maybe i should just ask the makers, lol

jamrock are you out of ideas?

actually, i had the same problem with win2k pro!! I could ping it, i had firewalls disabled, etc. i posted on here and had almost the exact post conversation as this one, everyone asking me if i had the domain name right, etc. The wierd thing about mine is it worked, then it didn't. i didn't change anything at all but it just didn't work anymore. The only fix i had (and this is a home network so i was able to use this) was to say "Fuck samba" and switched everything to use ssh. I dont know if this is a possibility with a need to use other applications but it damn sure worked good for me and i haven't had one single stupid problem that there is no apperent solution for like i did when i used samba. I know this isn't a solution to your problem but maybe you will feel better knowing that samba and win2k is a bitch to get working and more of a bitch to keep working. Don't know why but it is.

Apologies if this has been tried already...

I found that i can only access my Samba server using the IP address..

eg...

\\192.168.0.1\sharename

and i find that this doesnt work for some reason..

\\sambabox\sharename


This is from WinXP pro to SuSE 8.2

I adpreciate your replies. and through my personal experience, sambs never been a utter bitch.

All my machines except the 2k Server can connect, via netbios name or via ip. Neither ways work for the 2k Server.

I've been thinking.. my 2k server does use 2 nics, and because it isn't "advanced server" i had to use some registry settings to setup the network load balance.

Strangely it had worked for 5 minutes, and I didn't change a single setting, and since those 5 minutes, it stopped working.

I absolutely need my 2k server to access the samba.
I'm almost tempted to actually call one of the team members cell phones... to get this resolved... lol

HECK I am so tired of all the problems trying to get SAMBA and Vendow$ to coperate that I am willing to try anything short of suiside....

then how would one setup a small script to connect to a windows share, copy files, and disconnect without using "mount -t smbfs" etc.

Because unfortunatly there seems to be a problem where I've crontabbed my script. (i tested it over 15 times to make sure it worked flawless). And after about a day or 2, there was over 150 samba processes.. LOL i had to reboot it.

FTP is out of the question

I guess no ones up to the challenge.

you know Hack I beggining to beleive that Samba is a fruit cake made in hell.
I am now reinstallin Linuxonce more going back to SuSe 8.2 Pro.
I may call them tomorrow and get some real help here.
I know one thing I will not install Samba using the factory software I will just down load the Tarball and go from there.

Let you know more later,
ikw38

ya im bout to uninstall the rpm and go with beta3 from tarbell

Hmm...

Whenever you are having a Samba problem, please post the smb.conf file, and also give us more information.

What is the domain name on your network?
Do you have security=DOMAIN in the smb.conf?
Is DNS setup properly?

Need more info

Don't know about that. I have set up quite a number of Samba networks. Never had a problem. It is just something simple that you are overlooking.

Ikw38,

Try a clean re-install of Samba and go through the IBM tutorial step by step. I have used that tutorial time and time again. Make sure you are using a version of Samba 2.2.7a or higher. Make sure you include domain logons = yes

Hakcenter,

Try setting both network cards to the same subnet. I can't think of any reason why you aren't getting through. I have to assume that there is something weird set up somewhere.

Is it using one network card now and the next one in 5 minutes?
Some kind of round robin logic?

Let us see your smb.conf file.

Are you logging on as the same user on the server and on the workstations?

What happens when you run \\xxx.xxx.xxx.xxx and use the i.p. address of the Samba machine?

When logging on to the server, do you log onto the local machine or on to the domain?