similar to: Win2K unable to see shares

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

Greetings, O Mighty SAMBA masters. A problem cropped up with our SAMBA implementation, which began when we upgraded the Sun Ultra 3000 on which it runs from Solaris 2.5.1 to Solaris 2.6. Our NT servers are no longer able to connect the the file services offered from that box, or at best, only intermittently. I began going through the "Diagnosing Samba" document (the one on the web

Hi , I am using Mandrake 7.2 and trying to install samba to share my linux hard disk with Windows 98 ... Herewith my config and diagonstics : bigserver <------------> aclient runing : mandrake 7.2 Win98 Ip Addr.: 192.168.0.1 192.168.0.2 password encrypted activated activated - ping commands work fine on both ways, so my Tcp/ip

Hi all, I am running RedHat 7.3 and Samba 2.2.3a. I am using DHCP for my Linux box (hostname: NGPLinux, IP 132.189.26.62). I can see the list of shares I defined by using "smbclient -L NGPLinux -N". I can resolve the name using "nmblookup -U 127.0.0.1 NGPLinux". However, when I tried to use "nmblookup -B 132.189.26.255 NGPLinux" on the local machine, I got the

dear Sir, i am running red hat 6.2 on one machine and windows 95 on another but i am unable to see the linux machine in my windows pcs network neighborhood.to check my samba server i tried the tests given in DIAGNOSIS.txt.I am able to run tests 1 to 4 without error but in test 5 which says ::: "test 5 : run the command "nmblookup -B ACLIENT '*'" You Should Get The

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

I am running Red Hat 7.3 and samba 2.2.3a I can see the samba server in network neighborhood however when I try to connect I receive the following error: \\Puddles is not accessible A network error has occurred. You might not have access to some network resources my smb.conf file is as follows: [global] workgroup = POND encrypt passwords = yes security = SHARE [homes] guest OK =

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 want to share my linux printer with my windows laptop. The printer is attached to box with redhat 7.2 and samba-2.2.1a-4. The laptop runs windows 98 and they are connected by a netgear RP114 router. I have been following DIAGNOSIS.txt. I had trouble with the test 2, "ping ACLIENT" and "ping BIGSERVER" until I added ACLIENT to /etc/hosts on BIGSERVER and added BIGSERVER to

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

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 am running Red Hat 7.3 and samba 2.2.3a I can see the samba server in network neighborhood however when I try to connect I receive the following error: _ my smb.conf file is as follows: [global] workgroup = POND encrypt passwords = yes security = SHARE [homes] guest OK = yes read only = no path = / [AllFiles] path = / read only = no Testparm yields no errors I have

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

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

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

Well gang, I'm back and still haven't figured out why Samba isn't working with my Windoze PC's. I though I was close a couple times, but now I'm back to square 1. So now I'm going to spill as much information on you guys as I can in the hope that someone will notice what I'm doing wrong and help me get this thing running. Here are the computers on my home network:

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

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.

Everything else works, but "nmblookup -B ACLIENT '*'". It shows the servers IP address, unless "ACLIENT" can be resolved thru hosts/dns. Can someone explain me why? Samba 2.0.5b on Linux 2.0.36 name resolve order = lmhosts host wins bcast dns proxy = No wins proxy = No wins server = mywinsserver.mydomain wins support = No

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