similar to: Multiple configuration problem

I make all steps in the guide: http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/install.html#id2546028 but command (exetuded in the same computer where is samba): smbclient //fc9/tester -Utester%test gives error: Domain=[DZTI] OS=[Unix] Server=[Samba 3.2.0-17.fc9] tree connect failed: NT_STATUS_BAD_NETWORK_NAME The user tester have been created by commands: useradd tester smbpasswd -a

> Maybe there isn't a glibc version (although > it shouldn't be hard to port the Solaris version to >glibc). I will try to port nss_wins to glibc. I made some changes to smb.conf and follow the tests described in Samba diagnosis (www.samba.org/samba/docs/diagnosis.html) smb.conf [global] workgroup = NETMANAGER server string = Deltacom Samba Server printcap name =

I'm running Samba on my Sun ultra 1 with Solaris 2.6 and have noticed that my log.nmb file is growing tremendously. In addition, my log.smb is also growing but not quite as fast. The log.nmb has the following entries repeating every few seconds. Since 3/18/99, my log.nmb file has grown to be 22mb. [1999/06/14 09:13:14, 1] nmbd/nmbd.c:(672) Netbios nameserver version 2.0.0 started.

Hi, first of all, my apologies for the very technical and long nature of this message... I still do not give up with the problem I am having about not being able to browse the Network Neighborhood sometimes. My original post to the list was: >I am using Windows 95 dial-up networking to connect to a Samba box (the >Samba box is a PPP server). I am having problems to browse the Network

Rob, Don't know how this one got on samba-docs but I am forwarding it to the main samba list. Thanks. Cheers, jerry Rob Malpass wrote: > > So your Linux box can see your Windows machine but Windows can't see your Linux box ? > > If this is caused by upgrading to 2.0.6 I can't offer much help. Sounds like you've done the obvious things e.g. > > 1)

Hello, I am running the following OS CentOS 5.2 Samba Release samba-3.0.28 Kernel 2.6.18-92.1.22 (latest from CentOS) I also tried compiling a custom kernel with the experimental MSDFS option in kernel version 2.6.28.7 to no avail. Microsoft Server OS Windows Server 2003 R2 My Samba server has winbind enabled and the following smb.conf configuration. [global] socket options =

Hi list. I'm new to this list, so please bear with me. I've got samba 2.2.8a on Solaris 9 (SPARC). I've run all the tests. testparm runs fine. Other tests: # nmblookup -B stage __SAMBA__ querying __SAMBA__ on 192.168.18.25 192.168.18.25 __SAMBA__<00> # # nmblookup -B 192.168.1.9 '*' querying * on 192.168.1.9 192.168.1.9 *<00> # # nmblookup -d 2 '*'

Hi, I can't get "net view \\<servername>" to work from my Windows test client. It fails with "The network path was not found". I followed some of the online debugging guides and have found that a couple of the test nmblookups on the server are failing. The server is named 'fileserver1' and its IP address is 155.2.196.251 for the purpose of this email.

I'm trying to troubleshoot a new samba setup on a tiny network, and I'm clearly missing something. I'm running Samba 3.0.22 on Ubuntu Linux. When I first set it up, it seemed to go so smoothly. I changed all the workstations to the same workgroup (RABNETWORK) and they could see each other and the server, but they couldn't open anything on the server. I don't really understand

Believe me, I have tried everytbing I can think of to solve this problem. I will work my tail off to resolve this but I am fresh out of ideas. Any suggestions would be GREATLY appreciated. Here are the details... problem: server can see machines/shares on clients but clients cannot see machines/shares on server workgroup/domain: golgerth no router server: rpms: kernel 2.4.18.19.8.0

Before I reinvent the wheel, I wanted to find out if anyone has developed any scripts, and has made them available, that extract data from the Samba log files? More specifically, I want to use the information in the Samba log files to create a "database" that shows the date/time a user connected to a share and then logged off. The script would run daily and extract the most recent

This is getting real tough to debug. titan : Solaris 8 running samba 3.0.31 aequitas : OpenSolaris running samba 3.2.0 I can do basics test just fine : # /usr/xpg4/bin/date -u;/opt/csw/bin/findsmb Sat Jul 12 22:50:51 GMT 2008 *=DMB +=LMB IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION

Samba not responding to broadcast calls from networked PCs. Short: My Redhat Linux 8.0 box is not replying to udp broadcasts, and I can't figure out why. Network: The offending Redhat 8.0 Linux Box (//DS) attempting to run Samba 2.2.7 Firewall Redhat 7.3 (//IW) successfully running Samba 2.2.4 Win98 (//MS) Win2k (//SL) <Not running at the time of these tests> Very long: I've

I used to be able to browse the windows shares on the network through Nautilus. I can see them as computers, but when I click on them, it fails. (I'm on Ubuntu 6 LTS, AMD64) About 3 months ago, this failed. But, the windows boxes can all still access my shares on my Linux box. I was going through the trouble shooting, and found this out, but I'm not sure what to do next. I am

I'm debugging my Samba setup using the "Troubleshooting Techniques" from Sam's Teach Yourself Samba in 24 Hours. Everything works fine up until the nmbd section. I am able to do the following correctly: nmblookup -U 127.0.0.1 __SAMBA__ nmblookup -U 127.0.0.1 POGO (the server) nmblookup -B 192.168.1.255 WIN-CLIENT (the client) but when I do nmblookup -B 192.168.1.255

Hi All, Due to a hard-disc crash, I have just upgraded from a working Samba setup running in FC2 to a non-functional Samba setup running in FC3. The Windows XP machine has not changed, but won't connect. Samba is fully up2date from the FC3 repositories. smb.conf [global] workgroup = MYGROUP server string = Samba Server hosts deny = ALL hosts allow = 192.168.1.0/24 127.

Troubleshooting steps fail. Trying to replace a standalone Netware server with a Samba4 server with AD. To isolate this test setup, changed server's static IP address and separated the wiring. Then went through the Troubleshooting portion of The Samba Checklist. Some tests pass. Some tests fail. I'm weak on Samba, DNS and AD. I appreciate your instructions on how to overcome the

It's really weird how many times thing break in threes. This time is was my wife's laptop, my router and a phone. Anyway... My network has a router and 2 computers; my F11 box with the samba server on it called steve and my wife's laptop now running Windows 7 called Kellie-PC. My old router was a Linksys WRT54G that I had flashed with DD-WRT. I was using DHCP and DNS masquerading in

Hello all. I've decided to try using samba on our Solaris systems to give users who are stuck with PCs on their desks access to our gis data. I obtained a compiled binary package of version 2.0.7 from one of the samba.org sites, and have installed SAMBAroot, SAMBAusr, SAMBAman, and SAMBAdoc. All apparently worked just fine. I've made a couple of changes to the smb.conf file, changing

Hi, I've a got kind of weird problem using nmbd. At least, I think is is weird because this problem isn't dealt with in any documentation. I got my nmbd up and running, when I issue the command 'nmblookup -U 10.0.0.1 __SAMBA__' (my IP is 10.0.0.1/255.0.0.0) I get a correct response: 'querying __SAMBA__ on 10.0.0.1 10.0.0.1 __SAMBA__<00>' But when I use a