I hope you used a domain you registered, or one that can't be registered and thus cause conflicts. Seeing how mydomain.com is registered by dotster, I think that is probably not you. Don't just pick registrable domains, please.

> option domain-name-servers ns1.mydomain.com, ns2.mydomain.com;

This doesn't work. Use ip addresses.

> option subnet-mask 255.255.255.0;

Probably better to move that into the subnet declaration.

[snip]
> ddns-update-style interim;
> ddns-updates on;
> ignore client-updates;

I'd turn all that off until you get dhcp working. After that you can figure out ddns-updates.

> subnet 192.168.0.0 netmask 255.255.255.0 {
> range 192.168.0.10 192.168.0.30;
> option routers ns1.mydomain.com;

Better use an IP address here.

> option broadcast-address 192.168.0.255;
> } [snip!]
> Does anyone know how i can fix it?

The first thing to fix is your question: You only say "it does not work", but don't say just what exactly doesn't work. The dhcpd can be made to generate logs of what is happening. We need to see the bits pertaining to windows clients trying to obtain leases.

Also, you set your dhcpd to do dns-updates. Since your configuration seems to be rather arbitrary I suspect you might not have a dns setup to allow for that, or even dns setup at all. I would strongly suggest you turn off all dynamic updating first: Setup simple forward and reverse zones first, using a .local, or a domain you actually have registered yourself. Once that works, you can venture into getting ddns working.

-- j p d (at) d s b (dot) t u d e l f t (dot) n l . This message was originally posted on Usenet in plain text. Any other representation, additions, or changes do not have my consent and may be a violation of international copyright law.