[2004/05/18 04:52:02, 0] smbd/server.c:main(791)
smbd version 2.2.8a started.
Copyright Andrew Tridgell and the Samba Team 1992-2002
[2004/05/18 04:52:02, 0] smbd/server.c:main(835)
standard input is not a socket, assuming -D option
[2004/05/18 04:52:02, 0] lib/util_sock.cpen_socket_in(804)
bind failed on port 139 socket_addr = 0.0.0.0.
Error = Address already in use

this is from the log.smbd

my server is connected to my router just like all my other computers

if that makes any difference..

also when i click on (in my networkplaces) slackserver i can log in as user and pass user and it shows up with 2 directorys my user dir and netlogin that i don't have access too

i also have print and fax services that show up as well odn't know why but i do

i can ssh with user/user to my server as well


when i do the command testparm everything shows up fine



this is the full detail i get with windows

Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt.

The domain name Domaintest might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain Domaintest:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.Domaintest

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

- One or more of the following zones do not include delegation to its child zone:

Domaintest
. (the root zone)

For information about correcting this problem, click Help.


time for sleep..... brain exhusted....

i was getting some weird nmbd errors too

so i took out rc.samba from rc.d and uncommented smbd and nmbd in inetd.conf file and reboot

that took care of the nmbd error


still getting that same log.smbd error tho

Well, as we can see, smbd is failing to start properly.

From the looks of it, some other service is using port 139. Do you have any idea what it could be?

Stop Samba and do:

netstat -a

Check the output of that and see if anything is listening on port 139. Figure out what it is, and either disable it, or make it listen on another port.

Port 139 is the NetBIOS service. Without this, the Windows machines are not going to be able to find the domain controller.

While you can ping it, I think you will find that if you try to ping the Slackware machine by it's hostname from the Windows machine, you will not be able to do so.

This is because while the Slackware machine has a correct IP, Samba is unable to bind this to a NetBIOS name that Windows can identify with.

As a quick fix, you could put the Slackware machine's IP in when you try to join the domain. Windows should be able to contact it then, but it would be better to fix the error than do a messy hack.

Plus, Samba failing to properly bind a NetBIOS address might cause some instability or loss of functionality in smbd.

well i am using nmbd as well...

and i can ping the slackware machine

ping slackserver works just fine

but i can't do that until i run nmbd
it does run at start

Both smbd and nmbd are supposed to start at boot. You need both.

How are you starting them? And did you find anything listening on port 139?

umm there started in the inted.conf

and i didn't see anything listening on port 139
as far as netstat -a goes...

You should use the rc.samba script to start them instead.

Comment them out of inetd.conf and make rc.samba executable, then see if you still get that error when it starts.

ok
no more smb error now that i started it in the rc.samba

but nmbd starts in there too
and i am getting this error with log.nmbd


[2004/05/20 00:11:01, 0] nmbd/nmbd.c:main(795)
Netbios nameserver version 2.2.8a started.
Copyright Andrew Tridgell and the Samba Team 1994-2002
[2004/05/20 00:11:01, 0] nmbd/nmbd_subnetdb.c:create_subnets(239)
create_subnets: No local interfaces !
[2004/05/20 00:11:01, 0] nmbd/nmbd.c:main(873)
ERROR: Failed when creating subnet lists. Exiting.


and i cant connect with the netbios name from windows
i don't know if this has something to do with what you asked me to do... since i see the computer main listed there ....
MAIN is the computer that i was trying to get workin in the domain..

well i am going to be formating the drive and installed slackware current in about an hour

hopefully this can work stuff out

i will let you know any problems/errors i encounter after the installation


update:


well i got everthing installed

now running version 3.0.4 of samba


changed the workgroup to MSHOME
in my smb.conf

tried to connect my xp box to the domain MSHOME

no go so far


i get no errors in my log.smbd or log.nmbd now and everythign works fine for my server expect making a PDC

please please help me

i would like to get this solved soon

well i finally figured it out for my self

thanks

basically you forgot to put domain logons = yes
in your smb.conf file that you posted

so i finally figured that out