H
Henry Markov
My application is built around a service with an automatic start type. The
service determines the IP addresses of its host's ethernet ports and then
broadcasts capabilities messages on these ports. Clients that see these
broadcasts can make a connection for services. This application has worked
correctly with SP1 and gigabit ethernet ports for about a year.
I upgraded to SP2 and with all else being the same it appears that the DHCP
protocol takes much longer to complete. When my service determines the ethernet
port's IP address it gets the loopback address (127.0.0.1) rather than a DHCP
address. So I put the code in a loop whereby it continues to interrogate for
the IP address until it gets a valid DHCP assigned address. For reasons I don't
understand, after 30 seconds and after still not getting a DHCP address the
service terminates. There are no 30 second timeout hints in my service code.
In SP1 the loopback address is never returned when the code interrogates for the
port addresses. After the service quits I can do an ipconfig from the console
and typically see that some or all of the 3 ethernet ports still do not have
DHCP IP addresses. Several ipconfig attempts later the ports get addresses.
Why is the DHCP client in SP2 so extraordinarily slow compared to SP1? I
searched for methods to sequence system initialization such that I could be sure
that the DHCP client completed before my service loaded. The only thing I could
come up with was service LoadOrderGroup but I could find no usable documentation
on how to use this capability and it doesn't seem like a complete answer anyway.
Henry
service determines the IP addresses of its host's ethernet ports and then
broadcasts capabilities messages on these ports. Clients that see these
broadcasts can make a connection for services. This application has worked
correctly with SP1 and gigabit ethernet ports for about a year.
I upgraded to SP2 and with all else being the same it appears that the DHCP
protocol takes much longer to complete. When my service determines the ethernet
port's IP address it gets the loopback address (127.0.0.1) rather than a DHCP
address. So I put the code in a loop whereby it continues to interrogate for
the IP address until it gets a valid DHCP assigned address. For reasons I don't
understand, after 30 seconds and after still not getting a DHCP address the
service terminates. There are no 30 second timeout hints in my service code.
In SP1 the loopback address is never returned when the code interrogates for the
port addresses. After the service quits I can do an ipconfig from the console
and typically see that some or all of the 3 ethernet ports still do not have
DHCP IP addresses. Several ipconfig attempts later the ports get addresses.
Why is the DHCP client in SP2 so extraordinarily slow compared to SP1? I
searched for methods to sequence system initialization such that I could be sure
that the DHCP client completed before my service loaded. The only thing I could
come up with was service LoadOrderGroup but I could find no usable documentation
on how to use this capability and it doesn't seem like a complete answer anyway.
Henry
