similar to: How to find all workgroups being used on a subnet?

We're running an older version of Samba on an Irix machine, and just got 2.0.2 working (finally!) on our Intel/Linux box. The odd thing, is that findsmb gives different results on the two systms. On Irix it lists the NetBIOS names with OS descriptions, but on Linux it lists the IP name and no OS description. I went through it line by line and found the first difference at: ../nmblookup -r

The samba configuration on the local LAN works great but, I am trying to set up samba to permit browsing of two workgroups on different subnets and getting very close but not quite the results I want. Remote shares can be mapped to a local drive using "net use * \\remotehost\remoteshare" but in windows explorer the remote workgroup is not browsable : there is a "computer could not

My network looks like this: internet 192.168.0.0/24 router ----+----+----+----- internal 192.168.5.0/24 | | | router ----+-----+------+- LNB--->mswin | | (also a | | | client | | samba | | .... | | server) | | samba | | samba

I've tried building it on a server that I know has pretty much every library possible for a program to need, but I'm still not getting a good samba install. I'm on white-dwarf linux (kernel 2.4.25), gcc 3.3.2, Samba 3.0.2a White-dwarf is home-grown, very much like slackware. When I configure and make and make install, I don't get any errors, but I when I look for some files

Is it possible to ask a machine for its NetBIOS name if it's running either Windows or Samba? I tried a few various nmblookup and smbclient command lines to no avail. I would like to be able to query a machine (by IP) and have it respond with its nb name. I've noted that if I perform an smbclient -L -I on a machine, it will not list its shares unless I get the NetBIOS name correct...

Hi All, I have a openvpn setup between two Linux boxes. The internal networks on each side are on seperate network ranges. I can ping all boxes from either side, and if I search for a box using it's ip address, I can see the box and access it's shares. What I would like to do however is to be able to see the the pc's in their workgroups (each subnet has it's own workgroup). I

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, I looked through the archives, but didn't see anything like this. I have a network with a mix of Win95, Win98, and WinME clients (and one Linux system w/ Samba server version 2.2.2). All systems belong to a workgroup called "Oteima". All Win95 and Win98 clients see all other systems (including the Linux box) in one list.

> > acquired and configured SAMBA for basically one reason, that being to gain > > WINS client capabilities for AIX. Right now it's not working as expected, > > though. > > hi scott, > > we use gethostbyname(), which is wrapped by "dns proxy = yes/no" in the > samba WINS server code. it sounds like you want something similar, but > just using a

I'm trying to determine if the global configuration options for remote announce and remote browse sync work for browsing a different workgroup in a different subnet. In the books I have, it just talks about using these options to span the same workgroup across two subnets. In our situation, for example, I have two different workgroups (WG1 - 10.50.50.1 and WG2 - 10.100.50.1). Each of these

Hi all, Yesterday, i changed from samba 2.2.3 to samba 3.0, and also i changed the machines which samba is running on. Samba worked and should work as a PDC. It runs on a Debian sid, the test client is a notebook with XP Professional. Yesterday, immediately after migrating, everything worked fine. Even after several reboots, i could logon as a domain user, and i could use the shares. Today, i

Howdy people, How can i resolv a little thing that i have here. Why findsmb doesn't show me the computer if it is using the SP2 (win xp) ? I use findsmb alot. Jorge Bastos

Hello. Laptop with windows 7 pro 32 bits (192.168.130.66) does not respond to nmblookup. But from the Laptop with windows 7 (192.168.130.66), using explorer.exe I can browse the content of the public ressource on the serveur //serveur-linux/publique I have update the windows 7 registry but it does not help. HKLM\SYSTEM\CCS\Services\LanmanWorkstation\Parameters DWORD DomainCompatibilityMode 1

Hi, I'm trying to set up browsing across subnets to provide an 'enterprise'-wide (sorry for the MS term ;-) browse list / Network Neighbourhood. I've read BROWSING.TXT, but I can't see how machines on different subnets in different domains/workgroups sync up (using Samba, anyway). On my local subnet, I've set up a clunky old Linux 386 (Samba 1.9.18p8) as the browse

hi, when i give samba a workgroup name with more than 15 characters [the limit for netbios names], nmbd is unable to participate in browse master elections. it appears that parts of internal samba code honor 16 characters and parts only honor 15. details: i used a workgroup name of nodomain.nowhere, 16 characters, on samba 2.2.1a. the samba box was the only member of this workgroup on the

Hello, I am hoping someone can help me.... I am trying to configure my samba...and the problem is the following: When I use nmblookup with -B option and Broadcast address it is impossible to find my samba server (named prova) that is: # nmblookup -B 10.254.14.127 prova querying prova on 10.254.14.127 name_query failed to find name prova If I do the same lookin up to another machine different

Hello. I'm using Samba 3.0.25a on FreeBSD-6.0. Samba is configured to be a PDC. Samba can't find its hostname via nmblookup: $ nmblookup -B 192.168.1.255 frontier querying frontier on 192.168.1.255 name_query failed to find name frontier If I query Samba via unicast, it answers OK: $ nmblookup -U frontier frontier querying frontier on 192.168.1.31 192.168.1.31 frontier<00> Also,

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

We have two sites, one samba wins server and one w2k server (supplied for a particular task by someone else) The two sites are "foo" and "bar" We have two workgroups, "local" and "vendor" "Vendor" workgroup is at site "foo" All of our computers are in the "local" workgroup, and everyone at our two sites can see all the

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