P
Palle
Is it possible to enable client DHCP logging ?
The reason for asking is that we have clients (Win 2k pro) roaming between
subnets and sometimes when they boot up att a new subnet they don't get a
address relevant to the current subnet, instead they get the old address. We
have 2 DHCP servers (Win 2k Server) providing services, one in the
156.51.10.x subnet, and one in the 156.51.3.x subnet, they are providing
superscope for each other in case that one goes down. Extract from the
servers DHCP log:
The client in this case is supposed to renew at the DHCPserver 2.
DHCPserver 1
10,03/31/04,07:55:23,Assign,156.51.70.12,LTPST18001.company.se,00034791E618
11,03/31/04,08:01:32,Renew,156.51.70.12,LTPST18001.company.se,00034791E618
11,03/31/04,08:10:13,Renew,156.51.70.12,LTPST18001.company.se,00034791E618
11,03/31/04,08:10:18,Renew,156.51.70.12,LTPST18001.company.se,00034791E618
11,03/31/04,09:09:12,Renew,156.51.70.12,LTPST18001.company.se,00034791E618
10,03/31/04,09:32:16,Assign,156.51.70.12,LTPST18001.company.se,00034791E618
11,03/31/04,09:32:21,Renew,156.51.70.12,LTPST18001.company.se,00034791E618
DHCPserver 2
15,03/31/04,08:01:32,NACK,156.51.70.12,LTPST18001.company.se,00034791E618
15,03/31/04,08:10:13,NACK,156.51.70.12,LTPST18001.company.se,00034791E618
15,03/31/04,09:32:16,NACK,156.51.70.12,LTPST18001.company.se,00034791E618
10,03/31/04,09:40:04,Assign,156.51.10.39,LTPST18001.company.se,00034791E618
The final Assign is accomplished by manually cleansing each DNS, WINS and
DHCP of all refersnces to LTPST18001.
Any ideas ???
The reason for asking is that we have clients (Win 2k pro) roaming between
subnets and sometimes when they boot up att a new subnet they don't get a
address relevant to the current subnet, instead they get the old address. We
have 2 DHCP servers (Win 2k Server) providing services, one in the
156.51.10.x subnet, and one in the 156.51.3.x subnet, they are providing
superscope for each other in case that one goes down. Extract from the
servers DHCP log:
The client in this case is supposed to renew at the DHCPserver 2.
DHCPserver 1
10,03/31/04,07:55:23,Assign,156.51.70.12,LTPST18001.company.se,00034791E618
11,03/31/04,08:01:32,Renew,156.51.70.12,LTPST18001.company.se,00034791E618
11,03/31/04,08:10:13,Renew,156.51.70.12,LTPST18001.company.se,00034791E618
11,03/31/04,08:10:18,Renew,156.51.70.12,LTPST18001.company.se,00034791E618
11,03/31/04,09:09:12,Renew,156.51.70.12,LTPST18001.company.se,00034791E618
10,03/31/04,09:32:16,Assign,156.51.70.12,LTPST18001.company.se,00034791E618
11,03/31/04,09:32:21,Renew,156.51.70.12,LTPST18001.company.se,00034791E618
DHCPserver 2
15,03/31/04,08:01:32,NACK,156.51.70.12,LTPST18001.company.se,00034791E618
15,03/31/04,08:10:13,NACK,156.51.70.12,LTPST18001.company.se,00034791E618
15,03/31/04,09:32:16,NACK,156.51.70.12,LTPST18001.company.se,00034791E618
10,03/31/04,09:40:04,Assign,156.51.10.39,LTPST18001.company.se,00034791E618
The final Assign is accomplished by manually cleansing each DNS, WINS and
DHCP of all refersnces to LTPST18001.
Any ideas ???