nmb broadcast address doesn't match my lan addresses

I have a home network that is comprised of several XP machines (DHCP) a win7 machine (DHCP) and an Suse server ver 11.4 with a static IP (192.168.1.48).

I have been struggling off and on for quite a while to get shares to work between windows and linux and finally am starting to get close. I have samba set up followind Swerdna’s tutorials

# Date: 2011-03-01
[global]
 workgroup = kings
 netbios name = fishserver
 name resolve order = bcast hosts lmhosts wins 
 server string =""
 passdb backend = tdbsam
 printing = cups
 printcap name = cups
 cups options = raw
 use client driver = Yes
 map to guest = Bad User
 local master = yes
 preferred master = yes
 os level = 65
 usershare allow guests = Yes
 usershare max shares = 100
 usershare onwer only = False
[printers]
 browseable = yes
 path = /var/tmp
 printable = yes
 create mask = 0700
 browseable = no
 guest ok = yes
[linux drive]
 comment = this is a share point
 path = /home/samba
 read only = No

 guest ok = yes

[brother2140]
 path = /var/tmp
 printable = Yes
 guest only = yes


and can see the linux share if I enter the linux machines IP address in the network places window for the windows machines. The linux box is set up with the same workgroup name as the windows machines but never shows up as one of the workgroup machines.

I recently tried some suggested console commands and found that the nmb broadcast address is being issued to 192.168.3.255 even though all ip addresses on my network are using 192.168.1.x addresses. I used the command nmblookup -f AMDHP where the machine AMDHP has an address of 192.168.1.x supplied via DHCP from my router. I think this is why the network neighborhood name of the linux machine is missing. Where is the broadcast address derived and how can I fix it? Any help is appreciated.

FYI - I can access the linux shares via IP address just fine.

Thanks,

Dan

On Sun, 27 Jan 2013 21:46:01 +0000, catfish1968 wrote:

> broadcast address is being issued to 192.168.3.255

This is correct.

“Broadcast” is an address that all machines use. With a network subnet
of 192.168.3.x, the broadcast address is 192.168.3.255.

That’s how broadcasts on an IP subnet work.

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

For additional info on using Samba, have a look at these two blogs:

Samba S.W.A.T. - Samba Web Administration Tool Setup for openSUSE: https://forums.opensuse.org/blogs/jdmcdaniel3/samba-swat-samba-web-administration-tool-setup-opensuse-76/

AND

SWAT - Samba Web Administration Tool - Setup & Creation Script - 1.04: https://forums.opensuse.org/blogs/jdmcdaniel3/swat-samba-web-administration-tool-setup-creation-script-1-03-105/

I suggest taking a new look at some other smb.conf examples as shown in my blogs. For manual edits of that smb.conf file, have a look here:

SYSEdit - System File Editor - Version 1.50: https://forums.opensuse.org/blogs/jdmcdaniel3/sysedit-system-file-editor-version-1-00-60/

Thank You,

“Broadcast” is an address that all machines use. With a network subnet
of 192.168.3.x, the broadcast address is 192.168.3.255.

I’m confused then, since my network addresses are on 192.168.1.x the broadcast would still work from a different subnet?

Thanks,

Dan

On Mon, 28 Jan 2013 00:46:01 +0000, catfish1968 wrote:

> I’m confused then, since my network addresses are on 192.168.1.x the
> broadcast would still work from a different subnet?

Ah ha, I hadn’t noticed the subnet was different - so in that case, no,
unless your netmask isn’t 255.255.255.0.

On the box in question, what’s the output of:

/sbin/ifconfig eth0

?

(Please put it between code tags)

Jim

Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

ok, thought something was funny lol.

Here’s the output

 
eth0   Link encap:Ethernet  HWaddr 00:18:F3:5B:A8:57  
          
 inet addr:192.168.1.48  Bcast:192.168.3.255  Mask:255.255.252.0
          
 UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          
 RX packets:147982 errors:0 dropped:25 overruns:0 frame:0
          
 TX packets:128961 errors:0 dropped:0 overruns:0 carrier:0
          
 collisions:0 txqueuelen:1000 
          
 RX bytes:22334127 (21.2 Mb)  
 TX bytes:195247570 (186.2 Mb)
          
 Interrupt:17

Thanks for looking

ok, saw the net mask was wrong to after changing to /24 the broadcast looks correct. Guess I need to research how the newmask changes the broadcast range, seems a little goofy but at least that looks right now.

Thanks for aiming me in the right direction.

Dan

woo hooo. For the first time ever my Linux machine shows up in the network neighborhood. Even my printer share is showing up. Very cool.

Not sure why my netmask was set the way it was but definate lesson learned.

Thanks,

Dan

uh oh, woo hoo’d too soon. Now the Linux box can’t browse the internet. Why would the netmask change ruin that??

Thoughts?

Thanks,

Dan

ok, woo hoo back. not sure what was going on but i needed a couple reboots for things to settle down. I now have internet back and samba still works.

Thanks

Open up terminal and post a new result here with the right mask, use the correct device name of your network connection if not eth0:

/sbin/ifconfig eth0

The netmask determines what part of the IP address sets the subnet and what part sets the node address on the subnet. The mask is some number of 1’s set from left to right. The more ones you set, the more subnet’s and the fewer nodes you can have while the fewer 1’s you set, the fewer subnet’s you can have, but the more nodes each subnet can have. A /24 is the same as 255.255.255.0, but look at it from being 1 & 0’s with 11111111.11111111.11111111.00000000 or 24 ones are set. Now consider a 255.255.252.0 is a 11111111.11111111.11111100.00000000 where the subnet’s are reduced by a factor of 4 while nodes are increased also by a factor of 4. But the real story is that the subnet’s don’t match and communication will not work properly.

Thank You,

On Mon, 28 Jan 2013 01:06:01 +0000, catfish1968 wrote:

> ok, thought something was funny lol.
>
> Here’s the output
>
>
> Code:
> --------------------
>
> eth0 Link encap:Ethernet HWaddr 00:18:F3:5B:A8:57
>
> inet addr:192.168.1.48 Bcast:192.168.3.255 Mask:255.255.252.0
>
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>
> RX packets:147982 errors:0 dropped:25 overruns:0 frame:0
>
> TX packets:128961 errors:0 dropped:0 overruns:0 carrier:0
>
> collisions:0 txqueuelen:1000
>
> RX bytes:22334127 (21.2 Mb)
> TX bytes:195247570 (186.2 Mb)
>
> Interrupt:17
> --------------------
>
>
> Thanks for looking

That makes perfect sense then - you’ve got a mask of 255.255.252.0, which
means that the broadcast address is correct for that subnet. :slight_smile:

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

On Mon, 28 Jan 2013 01:56:01 +0000, catfish1968 wrote:

> ok, woo hoo back. not sure what was going on but i needed a couple
> reboots for things to settle down. I now have internet back and samba
> still works.
>
> Thanks

Awesome, glad to see you got it resolved. :slight_smile:

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C