[wellylug] samba server and dhcp

Phillip Rose rosewong at paradise.net.nz
Sun May 9 11:13:33 NZST 2004


Still trying to sort out getting a WIN2K machine to view samba shares on a
LAN using dhcp.

At 00:32 09/05/04 +1200, Sam Cannell wrote:
>Odd.
>
>If you run ipconfig, what does it show you?

Here is a summary of some network info:

The cast of characters:
   apu 192.168.0.1 running Smoothwall Express 2.0 (updated with patches)
output of "uname -a":
Linux apu 2.4.25 #8 Mon Feb 23 14:06:26 GMT 2004 i586 i586 i386 GNU/Linux
(Configured as dhcp server, some log output below)

   monty (so far always assigned 192.168.0.199)
"uname -a":
monty 2.6.3-4mdkenterprise #1 SMP Tue Mar 2 07:00:53 CET 2004 i686 unknown
 unknown GNU/Linux
(Configured as Samba server, gets IP address from apu)
Perinent lines from monty's smb.conf (highlights only):
# workgroup = NT-Domain-Name or Workgroup-Name
   workgroup = SAJGROUP
   hosts allow = 192.168.0.  127.
   os level = 128
   domain master = yes
   preferred master = yes

Anything pertaining to WINS is left commented out.

   krusty (so far always assigned 192.168.0.200)
Microsoft WIN2K service pack 2
member of SAJGROUP workgroup
Obtains IP address automatically
Obtains  DNS server address automatically
Uses 192.168.0.1 (apu) as Gateway
C:\Documents and Settings\phillip>ipconfig
Windows 2000 IP Configuration
Ethernet adapter Local Area Connection:
        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : 192.168.0.200
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.0.1

This machine can ping monty by IP & by hostname* , access monty (samba
server) by hostname.
* I find I have to restart smb on monty after it boots up, otherwise krusty
can't find it at all.

   mojo (so far always assigned 129.168.0.198)
Microsoft WIN2K service pack 4 (there's a difference I wasn't aware of!)
member of SAJGROUP workgroup
Obtains IP address automatically
Obtains  DNS server address automatically
Uses 192.168.0.1 (apu) as Gateway
The output of "ipconfig" is the same as for krusty above, but lists
192.168.0.198 as its IP address.

This machine can't even ping monty by IP address (request times out).

>Also, there may be something useful in your logs.  It'll vary from
>distribution to distribution, but in Debian, /var/log/messages has
>information about what the dhcp server is doing:

Here are some lines from apu Smoothwall's /var/log/messages (I grepped on
dhcp). Does it look like apu's configuration could use some tweaking?
May  9 07:56:50 apu dhcpd: Wrote 3 leases to leases file.
May  9 07:56:50 apu dhcpd: Listening on
LPF/eth0/00:80:ad:75:2f:5b/192.168.0.0/24
May  9 07:56:50 apu dhcpd: Sending on
LPF/eth0/00:80:ad:75:2f:5b/192.168.0.0/24
May  9 07:56:50 apu dhcpd: Sending on   Socket/fallback/fallback-net
May  9 07:57:30 apu dhcpd: DHCPDISCOVER from 00:05:1c:19:da:f4 (krusty) via
eth0
May  9 07:57:31 apu dhcpd: DHCPOFFER on 192.168.0.200 to 00:05:1c:19:da:f4
(krusty) via eth0
May  9 07:57:32 apu dhcpd: if IN A krusty. rrset doesn't exist add 1800 IN
A krusty. 192.168.0.200: timed out.
May  9 07:57:32 apu dhcpd: DHCPREQUEST for 192.168.0.200 (192.168.0.1) from
00:05:1c:19:da:f4 (krusty) via eth0
May  9 07:57:32 apu dhcpd: DHCPACK on 192.168.0.200 to 00:05:1c:19:da:f4
(krusty) via eth0
May  9 08:03:31 apu dhcpd: DHCPINFORM from 192.168.0.200 via eth0: not
authoritative for subnet 192.168.0.0
May  9 08:03:31 apu dhcpd: If this DHCP server is authoritative for that
subnet,
May  9 08:03:31 apu dhcpd: please write an `authoritative;' directive
either in the
May  9 08:03:31 apu dhcpd: subnet declaration or in some scope thatencloses the
May  9 08:03:31 apu dhcpd: subnet declaration - for example, write it at
the top
May  9 08:03:31 apu dhcpd: of the dhcpd.conf file.
May  9 08:03:34 apu dhcpd: DHCPINFORM from 192.168.0.200 via eth0: not
authoritative for subnet 192.168.0.0
May  9 08:16:00 apu dhcpd: DHCPDISCOVER from 00:0e:a6:a1:12:f4 via eth0
May  9 08:16:01 apu dhcpd: DHCPOFFER on 192.168.0.199 to 00:0e:a6:a1:12:f4
via eth0
May  9 08:16:01 apu dhcpd: DHCPREQUEST for 192.168.0.199 (192.168.0.1) from
00:0e:a6:a1:12:f4 via eth0
May  9 08:16:01 apu dhcpd: DHCPACK on 192.168.0.199 to 00:0e:a6:a1:12:f4
via eth0
May  9 08:16:12 apu dhcpd: DHCPDISCOVER from 00:40:f4:7a:6b:8c (mojo) via eth0
May  9 08:16:13 apu dhcpd: DHCPOFFER on 192.168.0.198 to 00:40:f4:7a:6b:8c
(mojo) via eth0
May  9 08:16:15 apu dhcpd: if IN A mojo. rrset doesn't exist add 1800 IN A
mojo. 192.168.0.198: timed out.
May  9 08:16:15 apu dhcpd: DHCPREQUEST for 192.168.0.198 (192.168.0.1) from
00:40:f4:7a:6b:8c (mojo) via eth0
May  9 08:16:15 apu dhcpd: DHCPACK on 192.168.0.198 to 00:40:f4:7a:6b:8c
(mojo) via eth0
May  9 08:27:33 apu dhcpd: if IN A krusty. rrset doesn't exist add 1800 IN
A krusty. 192.168.0.200: timed out.
May  9 08:27:33 apu dhcpd: DHCPREQUEST for 192.168.0.200 from
00:05:1c:19:da:f4 (krusty) via eth0
May  9 08:27:33 apu dhcpd: DHCPACK on 192.168.0.200 to 00:05:1c:19:da:f4
(krusty) via eth0
May  9 08:42:12 apu dhcpd: DHCPREQUEST for 192.168.0.199 from
00:0e:a6:a1:12:f4 via eth0
May  9 08:42:12 apu dhcpd: DHCPACK on 192.168.0.199 to 00:0e:a6:a1:12:f4
via eth0
May  9 08:46:17 apu dhcpd: if IN A mojo. rrset doesn't exist add 1800 IN A
mojo. 192.168.0.198: timed out.
May  9 08:46:17 apu dhcpd: DHCPREQUEST for 192.168.0.198 from
00:40:f4:7a:6b:8c (mojo) via eth0
May  9 08:46:17 apu dhcpd: DHCPACK on 192.168.0.198 to 00:40:f4:7a:6b:8c
(mojo) via eth0
May  9 08:57:33 apu dhcpd: if IN A krusty. rrset doesn't exist add 1800 IN
A krusty. 192.168.0.200: destination address requir
ed.
May  9 08:57:33 apu dhcpd: Wrote 3 leases to leases file.
May  9 08:57:33 apu dhcpd: DHCPREQUEST for 192.168.0.200 from
00:05:1c:19:da:f4 (krusty) via eth0
May  9 08:57:33 apu dhcpd: DHCPACK on 192.168.0.200 to 00:05:1c:19:da:f4
(krusty) via eth0
May  9 09:16:17 apu dhcpd: if IN A mojo. rrset doesn't exist add 1800 IN A
mojo. 192.168.0.198: destination address required.
May  9 09:16:17 apu dhcpd: DHCPREQUEST for 192.168.0.198 from
00:40:f4:7a:6b:8c (mojo) via eth0
May  9 09:16:17 apu dhcpd: DHCPACK on 192.168.0.198 to 00:40:f4:7a:6b:8c
(mojo) via eth0
=============
Then it seems to start repeating itself.
<snip>

>If you manually assign the win2k machine an address on your network, can
>it ping the Linux PC?
No, it behaves exactly the same vis-a-vis the other computers. It can ping
apu and krusty by hostname and IP, but can't ping monty by IP address.

The only real difference I can see between the 2 Windows machines is the
fact that the "defective" machine has Service Pack 4, not 2 as in the one
that works.

Thanks again!
--Phillip




More information about the wellylug mailing list