Topic awaiting preservation: Windows XP and Samba problems (Page 1 of 1)

Hey, I have a linux box running Samba 3.4 as a file server for 6 Windows XP workstations.

Everything has been running smoothly up until 3 days ago. Every once in a while, users are not able to access their folder on the network.

Everyone has seperate file on the Samba box that is a mapped network drive on their workstations.

I have looked at the samba logs for the different users.

lib/util_sock.c : get_peer_addr(978) getpeername failed. Error was Transport endpoint is not connected



lib/util_sock.c : send_smb(630) Error writing 5 bytes to client. -1. (Connection reset by peer)

I looked in the samba log under my workstations IP and found this:

nmbd/nmbd_resonserecordsbd.c : find_response_record (220) find_respond_record: respons packet id 34757 received with no matching record.

Does any of this throw a flag to anyone? I am not sure what the problem is. It seems like Samba is not authenticating the user sometimes. Just not sure why.

Thanks in advance!

Later,

C:\

Try asking that question here.



.

-- not necessarily stoned... just beautiful.

i asked on a couple of different linux only boards. LinuxQuestions and a couple of others.

Later,

C:\

well, it seems that I found the problem. I needed to set the samba config file to use WINS then set each of the workstations to point to the Samba server under the WINS.

I wasn't doing this before, just used automatic private IP address. Since everyone has a static internal ip address, I just set that and then used the prefered WINS server pointing to the samba box.

everything seems to be working fine now but we'll see

just thought i'd post this incase anyone else has a similar problem.

Later,

C:\

CPrompt,

I'm glad you got it working. The reason I suggested that particular mail list is that I use it and have found it to be a good source of information. I have frequented linuxquestions before and found that they are not particularly responsive to a lot of the questions I ask.



.

-- not necessarily stoned... just beautiful.

well it wasn't a matter of me not wanting to take your advice, i just posted that question everywhere and nothing. even the samba irc didn't have much to offer.

actually, after i posted this, it seems that the problem persisted. So, i started doing a little more digging. I noticed that some of the errors I had were more related to networking problems with the ip address. Some of the workstations don't have static ip address. Found out we had a power outage over the weekend. So...when one of the machines came back up, it grabbed the IP address of my fileserver. There was the problem, a conflict of IP address.

I ran ipconfig on all the machines to see what their ip address was and sure enough one of them had the same ip address as my fileserver.

thanks for the help!

Later,

C:\