similar to: Unable to view samba shares

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

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

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'd like my Samba server to be a Domain Master Browser for a workgroup (let's call it 'ENGINEER'). I set it up according to BROWSING.txt, but yet Windows NT/95 PCs on other subnets are unable to browse and see computers on this subnet (even if those PCs are also in the same workgroup). It appears that the Samba is not acting as the Domain Master Browser ... at least as far as

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

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'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

I just installed Redhat 8.0, got the errata samba packages, but I still can't get Samba to work. I have gone through the Diagnosis.txt file with the following results: Test 1: everything appears OK Test 2: pings work both ways Test 3: OK Test 4: # nmblookup -B lion __SAMBA__ querying __SAMBA__ on 192.168.8.14 192.168.8.14 __SAMBA__<00> OK Test 5: # nmblookup -B cub '*'

Hi, I hope you can help! I am having problems getting samba to share across a large private network. The problem looks a bit like the problem is in resolving the name to an IP but I can't work out why. The network is a private (10.) network, and the PC's connecting to it are named and identified through Wins. All the PC's are running Novell clients to connect although a large

In short this is the problem. The XP Home machine called "misty" cannot see any other machines. It cannot see the Linux machines and it cannot see the XP Home machines or the XP Pro machine. In spite of this blindness it can map to all the XP machines and define so-called network places. But "misty" cannot map through the SAMBA protocal used by the Linux machines to make

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

Helo , System : redhat 8 DS: netcape 4.16 Samba version : RC1. I am upgrading from samba3b3. Everything ( except changing passwd for user xp pro PC and I try to use rc1 to resolve ) seems ok in beta 3. On rc1 I Can't connect For a few second I can do : nmblookup -S l1serv2 added interface ip=172.29.160.100 bcast=172.29.167.255 nmask=255.255.248.0 querying l1serv2 on 172.29.167.255 Got

Hi, After lots of struggle and rtfm I finally got most things running, except for 'nmblookup' and 'net getlocalsid' on the BDC. I'm not new to Samba, but plenty more to learn. Here's the setup in summary: system pdc is the PDC on subnet 192.168.0.0, running SuSE10.1, LDAP master, wins server, domain master browser, no iptables; system bdc is the BDC on subnet 192.168.2.0,

Hello, I'm having problems getting my samba setup to work at a little LAN i partially maintain. I've been reading quite a lot about what I could think of being related to my problems/setup, and I've also googled my ass off :( So here I am, resorting to you guys in hope of help =] Sorry to say, but I don't have much experience, and therefore I'm a bit lost at the moment. Not

Dear List, I hope someone could give me some explanation about above error/problem I got. I have 2 machines, one installed RH7.3 (IP ADDR. =10.1.45.12, host name = fk0000-msi-srv) and the other one, Mandrake8.2. (IP ADDR. = 10.1.45.13) Both machines use Samba 2.2.3a. At the RH7.3, I got following error if I connect from Mandrake8.2. $ smbclient -U% -L 10.1.45.12 added interface ip=10.1.45.13

Folks, I am stumped! I have followed every tech tip I could find and I am still unable to complete my SMB installation. Specifically, I fail Test 4 and Tests 9 and 10. I believe the problem has something to do with the NMBD configuration. Below are the parameters of our system. Any help is greatly appreciated. Brandon Stauber brandon@inetevents.com 310-889-9264 [Please respond

Hi there, i have Samba 2.2.7a running on FreeBSD-STABLE 4.7. I set up a few things and smbd and nmbd start up at boot, i can browse the net. However, nmblookup can only find IPs by SMB-names, but not SMB-names by IPs. Here is an example output of the failed lookup: %nmblookup -d 3 210.104.1.133 Initialising global parameters params.c:pm_process() - Processing configuration file

Hello. I have some problem, with a new configuration on a new PC. I want to setup a SAMBA PDC using an HOWTO. This howto was working on OPENSUSE 10.1 with a X86 processor and I have used it a lot of time. Now I use OPENSUSE 10.3. The new PC run a X64 processor. After the fresh install and following : http://samba.org/samba/docs/man/Samba-HOWTO-Collection/diagnosis.html I could not make

Newbie question. If I type nmblookup __some other machine__ I get the correct response from Samba. If I type nmblookup __mymachine__ then I get an error yhat it is not found. So if nmbd is not setup right, how do I fix it? --Dan Dan Huston Phone (602) 965-2420 Measurement, Statistics and Methodological Studies Fax (602) 965-0300 Psychology in Education

I've got Samba 2.2.2 installed and running fine on one of our servers (RS/6000 AIX 4.3.3 and using NT authentication), however, when I do Test #4 (from docs/textdocs/DIAGNOSIS.txt) it looks like this: npssrv{root}#nmblookup -B npssrv _SAMBA_ querying _SAMBA_ on 173.148.200.113 name_query failed to find name _SAMBA_ The test said I should get back the IP address of our samba server. I got