Gordon,
Thanks for your diplomatic letter on my rather stupid choice for a
netmask. Yesterday I found a web site on networking and read through it.
It helped considerably. I changed my netmasking to the following:
192.168.1.1 255.255.255.0
10.0.0.2 255.0.0.0
My systems seems happy with it, but Samba still isn't working:
>From /var/log/log.nmb:
[2000/08/17 15:42:56, 0] nmbd/nmbd_namequery.c:query_name_response(93)
query_name_response: Multiple (2) responses received for a query on
subnet 192.168.1.2 for name HOLINESS<1d>. This response was from IP
192.168.1.12
[2000/08/17 15:43:58, 0] libsmb/nmblib.c:send_udp(755)
Packet send failed to 192.168.1.255(138) ERRNO=Invalid argument
The Samba server on my Linux box can receive messages from the LAN but
can't reply. The Samba client, also on the Linux box, and ping are
accessing the LAN with no trouble.
On Thu, 17 Aug 2000, Gordon Messmer wrote:
>On Thu, 17 Aug 2000, Glen Lee Edwards wrote:
>
>> I have eth0 connected to the DSL modem (Cisco 675), 10.0.0.2. I have eth1
>> connected to the LAN, 192.198.1.1x.
>
>Are those the IP addresses of your ethernet cards, or the other machines
>on the network?
In my Linux box eth0 is 10.0.0.2 (WAN), eth1 is 192.168.1.10 (LAN)
WinPC 1 is 192.168.1.11 (LAN)
WinPC 2 is 192.168.1.12 (LAN)
>> 255.255.255.0, but my LAN was inaccessible - the two client machines
>> couldn't access the 'net through the Linux box.
>
>Could your "client" machines talk to each other?
Yes.
>Could they ping the
>Linux server's IP address?
No.
>> eth1 to 192.168.1.25 and now I have full access to the LAN (except my
>> Samba server on the Linux box won't run - don't know if this is related).
(Note: Since you responded to this I have changed the netmask to a legit
one, but the same situation as the preceeding paragraph exists.
Everything's working fine, IP packet forwarding, ping, can access the 'net
through the Linux box for DSL from the LAN, the WinPCs on the LAN can see
and access each other, but the Samba server can't respond to the LAN,
nor can the WinPC's see the Linux box from "Network Neighborhood".)
>It probably is related. A lot of SMB relies on being able to broadcast
>packets, and samba will probably reject your netmask since broadcast won't
>make any sense.
Makes sense. Who does the routing for the Samba server, Samba or the
kernel? If Samba is trying to send packets to 192.168.1.255 through eth0
that would explain the problem. 192.168.1.0 is eth1. BTW Samba worked
fine when the LAN was hooked to eth0. Might try that again.
>> only change I made to get this to work was in changing the netmask.
>
>Did you also change the netmask on the clients? How are they configured
>right now. (IP / Netmask / Gateway)
Yes, but I've since changed the Netmask:
WinPC 1 192.168.1.11 / 255.255.255.0 / 192.168.1.10
WinPC 2 192.168.1.12 / 255.255.255.0 / 192.168.1.10
Linux 1 192.168.1.10 / 255.255.255.0 / no gateway set
Linux 1 10.0.0.2 / 255.0.0.0 / 10.0.0.1
Hmmm. Maybe that's the problem. Maybe Samba is using the default
gateway, which goes to the LAN.
>> noticed in your example that you used the same netmask for both cards,
>> which would seem to negate my theory that 2 nics in the same box must have
>> different netmasks or one won't work.
>>
>> Also I've been told that 192.168.1.25 isn't a legitimate netmask, but
>> since the system is working I haven't changed it.
>
>The two network cards should have different network numbers, but usually
>the same netmask.
>
>Netmasks are composed of a number of bits which fill four bytes (32
>bits) starting from the most significant bit. That is, your netmask is a
>binary number like :
>11111111 11111111 11111111 000000000
>
>This netmask (for example) has 24 bits set to 1, and is ususually referred
>to as a twenty four bit netmask. If you translate each of the bytes to
>decimal, you get:
>255 255 255 0
>
>192.168.1.25 doesn't make sense as a netmask, since it looks like:
>11000000 10101000 00000001 00011001
>The bits don't fill from the most significant bit, and don't create a good
>"mask". This netmask will work for a few addresses, like 192.168.1.2 and
>192.168.1.4, but wouldn't for 192.168.1.3. It's just not a good thing :)
Ah. That makes sense. I was assuming that the netmask defined the
"street" that the network is on, but in reality it's the network address
as defined by the netmask.
I'll try changing the default gateway first, then the ethX cards next to
see if that gets Samba working. Any thoughts on the above are
appreciated.
Glen
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list