pantscat

Can you check if the following services are running? COM+ Event System Remote Procedure Call (RPC) DCOM Server Process Launcher I think these are the ones that DFSr is dependent on.

Have you done a chkdsk? Still nothing in the Event Viewer?

Can you start the DFSr service? I take it you have another DC?

Cool.

Does seem a bit odd. Probably worth running the usual things on it - DCdiag, chkdsk, etc...

Did it get wet? Remove the nic team, and just try it with a single nic.

I take it you want to migrate the database without having to recreate the scopes manually? If so... ensure your new server is authorised. Then - on the old server, open an elevated CMD prompt and type in: Netsh DHCP Server \\ Export c:\export\dhcp-database all Then on the new server, copy the exported files over, open an elevated CMD prompt and type in: Net stop DHCPserver Del c:\windows\system32\DHCP\DHCP.mdb Net start DHCPserver Netsh DHCP Server \\ Import c:\import\dhcp-database Exit Net stop DHCPserver Net start DHCPserver Hope that makes sense... - - - Updated - - - Oh, and of course stop the old dhcp service...

XTreeGold...

ISA, surely?

Cool - I stand corrected then!

I *think* you can configure static routes on the Sophos UTM...

You can configure VLANs on both of these models.

Yep, but VLANs are the key. As others have said, they're really not complicated once you get your head around it, and they'll definitely make management of the network easier.

How about a Procurve 6600 with the appropriate modules in the back? Meant the 5500... the 6600 is all 10gbe.

Yep - I think that's pretty much correct - the RED15 box creates a VPN tunnel back to your Sophos UTM so in effect it'll appear to the end users at the remote sites that they're on your LAN. In that case given your network, I'd go with a single subnet.

Will the sites be directly connected to you? Or is there a router in the way?

How's your network infrastructure? If it's a decent network, then you'll be able to do dynamic VLAN assignment (and therefore subnet assignment) by using 802.1x port authentication. Basically the switch asks the device that is plugged into it to authenticate and you can configure it to do so based on Active Directory groups. Then depending upon which group the PC is a member of will dictate which VLAN it gets assigned to. Also - if it's a rogue device (e.g. one that's not a member of your network) then it'll get chucked into an isolation VLAN where it can't talk to anything... so quite nice from a security point-of-view, too.

Because the devices will be on different subnets they won't be able to see each other or communicate with each other unless you setup routing between them either on your router or a suitable layer 3 switch.

Do you particularly want to maintain separate subnets? or will you be implementing VLANs to segregate traffic? If so - then a superscope is an option... otherwise I'd just change the subnet mask and adjust your DHCP scope.

Munki is worth a look at as a no-cost option.

Do you currently have 172.66.23.1 - 254? Those are public IP addresses, not private internal ones.

Yep... Step 2 ought to cover that.

No problem - feel free to shout if you need any pointers.

Hi, Yep - IPv4 is absolutely fine. In fact, technically, IPv4 is good for up to 16,777,214 devices, and very few organisations will be using IPv6 for internal addressing. What you need to do is change your subnet mask - so... The way I'd do it is this: 1. Edit your DHCP scope so that the lease time is down to something like an hour (or possibly less). 2. Change the configuration of all devices with fixed IPs to the new subnet mask. 3. Create a new DHCP Scope with the appropriate subnet mask and a new larger address pool. 4. Deactivate the old scope. 5. Do an "IPconfig /release" and "IPconfig /renew" on a few machines to make sure that they're getting the new scope settings from DHCP. 6. Wait an hour for all the others to catch up... Ant

Do you have the mac address of the device that is flooding the network? If you've got Procurve switches you can use the "show mac-address xx:xx:xx:xx:xx:xx" command to see what port the device is connected to...