Dear John:

[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!

Comments

[pyroofone.livejournal.com]

Not the worst Dear John letter one can receive.

[ladyfox7oaks.livejournal.com]

So... Just how bad is it when one gets a "Dear John" letter... from one's OWN BRAIN?

[zastrazzi.livejournal.com]

Probably depends on whether it actually packed up all it's stuff and left or not.

I might be comfy with the loss of some baggage :)

[ladyfox7oaks.livejournal.com]

TRUE!

[jsbowden.livejournal.com]

Those two IPs don't look the same to the domain controllers either. Your netmask tells it how many bits are on the local segment for routing decisions, it doesn't mask the actual IP address bits.

[theweaselking.livejournal.com]

I thought that, but saw the error and figured it was a stupid Windows trick.

And then my edit struck me.

Stupid!

[eididdy.livejournal.com]

I am pleased as punch that I could follow that.

[drjamez.livejournal.com]

For the record, I know an IT security department for a fairly large and rapidly growing New England based Toronto-based bank that set up a new security "appliance" and punched in THE CORE ROUTER FOR THE ENTIRE COMPANY'S ACCESS TO THE INTERNET as its IP address. They took down the entire network when the core router discovered the duplication and shut itself down until we corrected the issue.

But, I'm just sayin'. Lots of folks make mistakes and/or have "brain farts." At least you figured it all out. That's the important thing.

- James -

...who once said, "Wait, I thought I was logged onto the test server... what do you mean I rebooted the production database???? WHAT DO YOU MEAN YOU PUT THE BACKGROUND WINDOWS DESKTOP IMAGE TO THE SAME ONE AS ON THE TEST SERVER SO THAT THE TEXT IN THE LOWER RIGHT CORNER DISPLAYED THE WRONG NAME AND IP??? Holy crap...."

[theweaselking.livejournal.com]

I'm not saying I'm unique. Just that I was quite dumb.