Topic: Windows7 DHCP noise

[compsos]

This is only for information for those playing with Windows7 RC

Environment
SMEserver 7.4, VMWare ver2 , Windows7 RC VM Client on bridged eth0

We have not as yet got it to join the domain, but it seems to be creating a lot of noise, from an address set by MS, just to get a DHCP lease. The lease is eventually recognised by the mac address request.

This is what made us curious about the network connections. The windows failure to join diagnostics screen. Note the DNS IP address used.

Code: [Select]

The DNS servers used by this computer for name resolution are not responding. This computer is configured to use DNS servers with the following IP addresses:

192.168.1.254

Verify that this computer is connected to the network, that these are the correct DNS server IP addresses, and that at least one of the DNS servers is running.

Code: [Select]

May 24 12:23:08 server dhcpd: DHCPREQUEST for 192.168.1.100 from 00:0c:29:1c:e3:eb via eth0: wrong network.
May 24 12:23:08 server dhcpd: DHCPNAK on 192.168.1.100 to 00:0c:29:1c:e3:eb via eth0
May 24 12:23:08 server dhcpd: DHCPREQUEST for 192.168.1.100 from 00:0c:29:1c:e3:eb via eth0: wrong network.
May 24 12:23:08 server dhcpd: DHCPNAK on 192.168.1.100 to 00:0c:29:1c:e3:eb via eth0
May 24 12:23:08 server dhcpd: DHCPDISCOVER from 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:08 server dhcpd: DHCPREQUEST for 192.168.1.100 (192.168.1.254) from 00:0c:29:1c:e3:eb via eth0: wrong network.
May 24 12:23:08 server dhcpd: DHCPNAK on 192.168.1.100 to 00:0c:29:1c:e3:eb via eth0

=============
Repeated 70 times
=============

May 24 12:23:09 server dhcpd: DHCPNAK on 192.168.1.100 to 00:0c:29:1c:e3:eb via eth0
May 24 12:23:09 server dhcpd: DHCPREQUEST for 192.168.1.100 (192.168.1.254) from 00:0c:29:1c:e3:eb via eth0: wrong network.
May 24 12:23:09 server dhcpd: DHCPNAK on 192.168.1.100 to 00:0c:29:1c:e3:eb via eth0
May 24 12:23:09 server dhcpd: DHCPDISCOVER from 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPOFFER on 192.168.221.247 to 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPDISCOVER from 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPOFFER on 192.168.221.247 to 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPREQUEST for 192.168.1.100 (192.168.1.254) from 00:0c:29:1c:e3:eb via eth0: wrong network.
May 24 12:23:09 server dhcpd: DHCPNAK on 192.168.1.100 to 00:0c:29:1c:e3:eb via eth0
May 24 12:23:09 server dhcpd: DHCPREQUEST for 192.168.1.100 (192.168.1.254) from 00:0c:29:1c:e3:eb via eth0: wrong network.
May 24 12:23:09 server dhcpd: DHCPNAK on 192.168.1.100 to 00:0c:29:1c:e3:eb via eth0
May 24 12:23:09 server dhcpd: DHCPDISCOVER from 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPOFFER on 192.168.221.247 to 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPDISCOVER from 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPOFFER on 192.168.221.247 to 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPREQUEST for 192.168.1.100 (192.168.1.254) from 00:0c:29:1c:e3:eb via eth0: wrong network.
May 24 12:23:09 server dhcpd: DHCPNAK on 192.168.1.100 to 00:0c:29:1c:e3:eb via eth0
May 24 12:23:09 server dhcpd: DHCPREQUEST for 192.168.1.100 (192.168.1.254) from 00:0c:29:1c:e3:eb via eth0: wrong network.
May 24 12:23:09 server dhcpd: DHCPNAK on 192.168.1.100 to 00:0c:29:1c:e3:eb via eth0
May 24 12:23:09 server dhcpd: DHCPDISCOVER from 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPOFFER on 192.168.221.247 to 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPDISCOVER from 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPOFFER on 192.168.221.247 to 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPREQUEST for 192.168.1.100 (192.168.1.254) from 00:0c:29:1c:e3:eb via eth0: wrong network.
May 24 12:23:09 server dhcpd: DHCPNAK on 192.168.1.100 to 00:0c:29:1c:e3:eb via eth0
May 24 12:23:09 server dhcpd: DHCPREQUEST for 192.168.1.100 (192.168.1.254) from 00:0c:29:1c:e3:eb via eth0: wrong network.
May 24 12:23:09 server dhcpd: DHCPNAK on 192.168.1.100 to 00:0c:29:1c:e3:eb via eth0
May 24 12:23:09 server dhcpd: DHCPDISCOVER from 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPOFFER on 192.168.221.247 to 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPDISCOVER from 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPOFFER on 192.168.221.247 to 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPREQUEST for 192.168.1.100 (192.168.1.254) from 00:0c:29:1c:e3:eb via eth0: wrong network.
May 24 12:23:09 server dhcpd: DHCPNAK on 192.168.1.100 to 00:0c:29:1c:e3:eb via eth0
May 24 12:23:09 server dhcpd: DHCPREQUEST for 192.168.1.100 (192.168.1.254) from 00:0c:29:1c:e3:eb via eth0: wrong network.
May 24 12:23:09 server dhcpd: DHCPNAK on 192.168.1.100 to 00:0c:29:1c:e3:eb via eth0
May 24 12:23:09 server dhcpd: DHCPDISCOVER from 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPOFFER on 192.168.221.247 to 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPDISCOVER from 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPOFFER on 192.168.221.247 to 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPREQUEST for 192.168.1.100 (192.168.1.254) from 00:0c:29:1c:e3:eb via eth0: wrong network.
May 24 12:23:09 server dhcpd: DHCPNAK on 192.168.1.100 to 00:0c:29:1c:e3:eb via eth0
May 24 12:23:09 server dhcpd: DHCPREQUEST for 192.168.1.100 (192.168.1.254) from 00:0c:29:1c:e3:eb via eth0: wrong network.
May 24 12:23:09 server dhcpd: DHCPNAK on 192.168.1.100 to 00:0c:29:1c:e3:eb via eth0
May 24 12:23:09 server dhcpd: DHCPDISCOVER from 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPOFFER on 192.168.221.247 to 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPDISCOVER from 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPOFFER on 192.168.221.247 to 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:09 server dhcpd: DHCPREQUEST for 192.168.1.100 (192.168.1.254) from 00:0c:29:1c:e3:eb via eth0: wrong network.
May 24 12:23:09 server dhcpd: DHCPNAK on 192.168.1.100 to 00:0c:29:1c:e3:eb via eth0
May 24 12:23:09 server dhcpd: DHCPREQUEST for 192.168.1.100 (192.168.1.254) from 00:0c:29:1c:e3:eb via eth0: wrong network.
May 24 12:23:09 server dhcpd: DHCPNAK on 192.168.1.100 to 00:0c:29:1c:e3:eb via eth0
May 24 12:23:11 server dhcpd: DHCPDISCOVER from 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:11 server dhcpd: DHCPOFFER on 192.168.221.247 to 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:11 server dhcpd: DHCPDISCOVER from 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:11 server dhcpd: DHCPOFFER on 192.168.221.247 to 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:11 server dhcpd: DHCPREQUEST for 192.168.221.247 (192.168.221.1) from 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:11 server dhcpd: DHCPACK on 192.168.221.247 to 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:11 server dhcpd: DHCPREQUEST for 192.168.221.247 (192.168.221.1) from 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:11 server dhcpd: DHCPACK on 192.168.221.247 to 00:0c:29:1c:e3:eb (test7) via eth0
May 24 12:23:15 server dhcpd: DHCPINFORM from 192.168.221.247 via eth0
May 24 12:23:15 server dhcpd: DHCPACK to 192.168.221.247
May 24 12:23:15 server dhcpd: DHCPINFORM from 192.168.221.247 via eth0
May 24 12:23:15 server dhcpd: DHCPACK to 192.168.221.247


[dtech]

This is only for information for those playing with Windows7 RC

Environment
SMEserver 7.4, VMWare ver2 , Windows7 RC VM Client on bridged eth0

We have not as yet got it to join the domain, but it seems to be creating a lot of noise, from an address set by MS, just to get a DHCP lease. The lease is eventually recognised by the mac address request.

Gordon;

I've been following this discussion, looks like Windows 7 will not be able to join a NT4 domain.

http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/8b4dd460-dd57-41da-b541-6933cd4d2531

-dtech

[compsos]

Thanks for that Dtech

We had found all the other entries but not the DomainCompatibilityMode = 1

After applying it we joined the SMEServer but still throws errors after rebooting Win7. Win7 thinks it is trying to use a DNS server that does not exist. Would suggest that it is looking to 192.168.1.254. See 2nd box.

Now the client does not get a valid IP address. Guess we wait for MS to make it compatible with NT domains.

Code: [Select]

May 24 15:39:44 server slapd[4354]: conn=0 fd=7 ACCEPT from IP=192.168.221.247:49163 (IP=0.0.0.0:389)
May 24 15:39:44 server slapd[4354]: conn=0 op=0 SRCH base="" scope=0 deref=0 filter="(objectClass=*)"
May 24 15:39:44 server slapd[4354]: conn=0 op=0 SRCH attr=subschemaSubentry dsServiceName namingContexts defaultNamingContext schemaNamingContext configurationNamingContext rootDomainNamingContext supportedControl supportedLDAPVersion supportedLDAPPolicies supportedSASLMechanisms dnsHostName ldapServiceName serverName supportedCapabilities
May 24 15:39:44 server slapd[4354]: conn=0 op=0 SEARCH RESULT tag=101 err=0 nentries=1 text=
May 24 15:39:44 server slapd[4354]: conn=0 op=1 BIND dn="" method=163
May 24 15:39:44 server slapd[4354]: conn=0 op=2 BIND dn="" method=163
May 24 15:39:44 server slapd[4354]: SASL [conn=0] Failure: realm changed: authentication aborted
May 24 15:39:44 server slapd[4354]: conn=0 op=2 RESULT tag=97 err=49 text=SASL(-13): authentication failure: realm changed: authentication aborted
May 24 15:39:44 server esmith::event[6634]: Processing event: machine-account-create test7$
May 24 15:39:44 server esmith::event[6634]: Running event handler: /etc/e-smith/events/machine-account-create/S10create-machine-account
May 24 15:39:44 server /etc/e-smith/events/machine-account-create/S10create-machine-account[6635]: /home/e-smith/db/accounts: OLD test7$=(undefined)
May 24 15:39:44 server /etc/e-smith/events/machine-account-create/S10create-machine-account[6635]: /home/e-smith/db/accounts: NEW test7$=machine
May 24 15:39:44 server esmith::event[6634]: create-machine-account test7$: Creating Unix user and group
May 24 15:39:45 server esmith::event[6634]: create-machine-account test7$: Locking account
May 24 15:39:45 server esmith::event[6634]: Locking password for user test7$.
May 24 15:39:45 server esmith::event[6634]: passwd: Success
May 24 15:39:45 server esmith::event[6634]: S10create-machine-account=action|Event|machine-account-create|Action|S10create-machine-account|Start|1243143584 747794|End|1243143585 308929|Elapsed|0.561135
May 24 15:39:46 server dhcpd: DHCPREQUEST for 192.168.221.247 from 00:0c:29:1c:e3:eb (test7) via eth0
May 24 15:39:46 server dhcpd: DHCPACK on 192.168.221.247 to 00:0c:29:1c:e3:eb (test7) via eth0
May 24 15:39:46 server smbd[6631]: [2009/05/24 15:39:46, 0] rpc_server/srv_netlog_nt.c:_net_auth_2(478)
May 24 15:39:46 server smbd[6631]:   _net_auth2: creds_server_check failed. Rejecting auth request from client TEST7 machine account TEST7$
May 24 15:39:46 server smbd[6631]: [2009/05/24 15:39:46, 0] rpc_server/srv_netlog_nt.c:_net_auth_2(478)
May 24 15:39:46 server smbd[6631]:   _net_auth2: creds_server_check failed. Rejecting auth request from client TEST7 machine account TEST7$
May 24 15:39:46 server slapd[4354]: conn=1 fd=8 ACCEPT from IP=192.168.221.247:49164 (IP=0.0.0.0:389)
May 24 15:39:46 server slapd[4354]: conn=1 op=0 SRCH base="" scope=0 deref=0 filter="(objectClass=*)"
May 24 15:39:46 server slapd[4354]: conn=1 op=0 SRCH attr=subschemaSubentry dsServiceName namingContexts defaultNamingContext schemaNamingContext configurationNamingContext rootDomainNamingContext supportedControl supportedLDAPVersion supportedLDAPPolicies supportedSASLMechanisms dnsHostName ldapServiceName serverName supportedCapabilities
May 24 15:39:46 server slapd[4354]: conn=1 op=0 SEARCH RESULT tag=101 err=0 nentries=1 text=
May 24 15:39:46 server slapd[4354]: conn=1 op=1 UNBIND
May 24 15:39:46 server slapd[4354]: conn=1 fd=8 closed


Code: [Select]

May 24 15:43:22 server dhcpd: DHCPACK on 192.168.221.247 to 00:0c:29:1c:e3:eb (TEST7) via eth0
May 24 15:43:22 server dhcpd: DHCPDISCOVER from 00:0c:29:1c:e3:eb (TEST7) via eth0
May 24 15:43:22 server dhcpd: DHCPOFFER on 192.168.221.247 to 00:0c:29:1c:e3:eb (TEST7) via eth0
May 24 15:43:22 server dhcpd: DHCPDISCOVER from 00:0c:29:1c:e3:eb (TEST7) via eth0
May 24 15:43:22 server dhcpd: DHCPOFFER on 192.168.221.247 to 00:0c:29:1c:e3:eb (TEST7) via eth0
May 24 15:43:22 server dhcpd: DHCPREQUEST for 192.168.1.100 (192.168.1.254) from 00:0c:29:1c:e3:eb via eth0: wrong network.
May 24 15:43:22 server dhcpd: DHCPNAK on 192.168.1.100 to 00:0c:29:1c:e3:eb via eth0
May 24 15:43:22 server dhcpd: DHCPREQUEST for 192.168.1.100 (192.168.1.254) from 00:0c:29:1c:e3:eb via eth0: wrong network.
May 24 15:43:22 server dhcpd: DHCPNAK on 192.168.1.100 to 00:0c:29:1c:e3:eb via eth0
May 24 15:43:29 server dhcpd: DHCPINFORM from 192.168.1.100 via eth0: unknown subnet 0.0.0.0
May 24 15:48:51 server last message repeated 2 times

[dtech]

Looks like a little more information that might be useful:

http://lists.samba.org/archive/samba/2009-May/148164.html

Text of the post is:

Hi all,
> That won't work. Your only chance is Samba 3.3.4 with
>
>         HKLM\System\CCS\Services\LanmanWorkstation\Parameters
>             DWORD  DomainCompatibilityMode = 1
>             DWORD  DNSNameResolutionRequired = 0
>
>         HKLM\System\CCS\Services\Netlogon\Parameters
>             DWORD  RequireSignOnSeal = 0
>             DWORD  RequireStrongKey = 0
>
> Haven't tested that yet, but you should get some steps
> further.
>
> Volker
>   
I succeeded to join Windows 7(RC) to Samba 3.3.4 domain.

1. I installed Windows 7.
2. I changed above 4 parameters by regedit on Windows 7.
3. Windows 7 can join to the domain which is provided by Samba 3.3.4.

Great!

Yasuma Takeda

[dtech]

For fun I tried the workaround posted above, it didn't work for me on SME 7.4.

Also, I note that the HKLM entry in the instructions "RequireSignOnSeal" is wrong, it should be "RequireSignOrSeal", which is an existing key that by default is set to 1.

[globalsi]

Note :
If these keys not exist, you must create them

> HKLM\System\CCS\Services\LanmanWorkstation\Parameters
>             DWORD  DomainCompatibilityMode = 1
>             DWORD  DNSNameResolutionRequired = 0

globalsi

[CharlieBrady]

For fun I tried the workaround posted above, it didn't work for me on SME 7.4.

SME 7.4 does not have samba 3.3.4.

[globalsi]

Yes it still don't work...


Will SME8.x got samba 3.3.4 ?

[Stefano]

Will SME8.x got samba 3.3.4 ?

only if CentOS 5.X will.. but I'm pretty sure we have to wait for Centos 6 (maybe later)

[CharlieBrady]

only if CentOS 5.X will..

No, that's not necessarily true. The policy is that packages will be used directly from CentOS, unless there are compelling reasons to do otherwise. There may be compelling reasons in this case.

See http://bugs.contribs.org/show_bug.cgi?id=5425