search for: samba24hc13

I encountered the following problem, can anyone help me? when i use "nmblookup -B 192.168.1.255 redmaple" on my linux box named redmaple, something like "(tdb(null)): could not open file /usr/local/samba/var/locks/unexpected.tdb. No such file or directory" is output, and the name lookup failes. my samba is 2.2.3a, IP address of redmaple is 192.168.1.5 rgds aloha

Hi Everyone, >From windows 2K, machine I could see Samba server but I can't get its share. I tried to follow the instruction given at http://samba.planetmirror.com/samba/ftp/docs/Samba24Hc13.pdf to resolve the problem. nmblookup -U 127.0.0.1 _SAMBA_ and nmblookup -B 10.10.255.255 real-samba-server-name fails for me but nmblookup -U 127.0.0.1 real-samba-server-name works for me. Any idea what's going on? Thanks ----------------------------------- Parag Nag...

...am hoping that someone can help me. I have been trying for several weeks to get Samba working to no avail. I have consulted many online help files including the ones located at http://us1.samba.org/samba/docs/DIAGNOSIS.html, browsing.txt that comes with samba, http://us2.samba.org/samba/ftp/docs/Samba24Hc13.pdf, and a few others. I have even posted a previous message, which produced a some help, but with no success story yet. My configuration is: Red Hat 7.2 IP address: 192.168.1.6 Samba Server: 2.2.1a Samba Server Name: SAMBASERVER Workgroup Name: ABOGEXAM etc/hosts file contains: 127.0....

Hi everyone, I'm trying to set up a Windows XP Pro client to connect to a Samba server (version 2.2.8) on a Redhat 8.0 linux box, but have been having trouble for the past 3 days. I have gone through Troubleshooting Samba at [http://us1.samba.org/samba/ftp/docs/Samba24Hc13.pdf] but I can't figure out how to fix the problem. I suspect that the broadcast address may not be the same on both boxes, but how do I set that in Windows XP? The problem may be something else, so I'll try to be as specific as possible: The server ip is 10.0.1.201, named fizzlebox The wi...

I am running the diagnostics to figure out why my client machine can't talk to the samba server, here's what I was able to find out. I went through the Hour 13 Troubleshooting from the samba.org web site (http://us1.samba.org/samba/ftp/docs/Samba24Hc13.pdf) and I got all the way up to section where you test nmbd, and found the following problem: [root@server samba]# nmblookup -B 192.168.0.255 SERVER querying SERVER on 192.168.0.255 name_query failed to find SERVER What is annoying is that the client machine (MIKELAPTOP) is clearly seen in the...

...visable to Win2k machine. What doesn't work: Box comes up asking for user name / password, all combinations fail. (It does want a normal logon for the server, right?) Going through the troubleshooting techniques hour 13 on the samba site (http://us3.samba.org/samba/ftp/docs/Samba24Hc13.pdf) it said to try "smbclient //hostname/share -U user%pass". In my case smbclient //CheeZe/tmp -U user%pass. I try this while sshing into the Redhat system from the Win2k system. I get: Got a positive name query response from (IP) session setup failed: NT STA...

I have realised that using Samba is a complicated business and finding a simular scenario (and, hopefully, a solution) has proven to be more difficult than I would have thought. That is why I write to the samba list for help. I'm just kicking through leaves, while some of you guys *wrote* this piece of software!!! My setup is really simple. I've based the setup on the basic smb.conf that

I am running SAMBA on Red Hat 7.0 and after a bad upgrade my SAMBA server is dead. I ended up re-installing from the source and now my server is not accessible to our Win9x clients. smbstatus show the server running but no one on the network can see the server. I am still a bit of a newbie and I am having trouble troubleshooting this. I really am in a jam and I need some help ASAP. I am not