Dear John:

May. 29th, 2008 02:27 pm
theweaselking: (Default)
[personal profile] theweaselking
Dear John:

When you're setting up a new SBS 2003 Domain server, and you've got a router/firewall to hide it from the other, live, domain server so you can set up things like DHCP and "being a domain controller", and you keep having problems where it says the DHCP server can't start because it can see the other server no matter what ports or IPs you block on the router?

Check your wiring.

It REALLY HELPS if the new server is *not* on the same side of the firewall as the old one.

No Love,
John's Brain.

PS: 10.30.1.250 might not LOOK like 192.168.0.250 to you, but you aren't looking at it from behind a 255.255.255.0 netmask.
And since 192.168.0.250 IS looking at it from behind that mask, that means you've just added an IP address conflict with the domain controller.
YOU IDIOT.

EDIT:

PPS: Setting a static IP for the firewall = good.
Setting a static IP THAT ALSO MATCHES THE BLOODY DOMAIN SERVER = you fix that, unplug everything, and go home now. Come back later, try again. Gah!
This account has disabled anonymous posting.
If you don't have an account you can create one now.
HTML doesn't work in the subject.
More info about formatting

Profile

theweaselking: (Default)theweaselking
Page generated Feb. 7th, 2026 12:43 am