Avatar of JustAsk
 asked on

SBS 2008 Migration with public IP

Hi there

Doing a migration from server 2003 AD to a small business 2008 . Following the basic install for migration , but ran into one glitch.

Client uses Public IP's because of internal legacy business system and cannot change to private.addresses.

SBS 2008 hangs the point when it searches and find the router and says I have public IP's . I created and have mounted a USB key file with attended install to do the migration and list the public ip addresses in there.

Any ways around this , aside from dropping the 2003 server to private, which BTW will cause havoc in AD as ALL the rest of the domain would have to stay on the public ip for the term of the migration.

I assume after the successful migration I could change both ip's back to public, but I am sure will create more grief with basic 2008 setup.


Avatar of undefined
Last Comment
Rob Williams

8/22/2022 - Mon
Rob Williams

Unfortunately SBS 2008 supports only one network adapter, therefore it must be a private IP, unless of course all devices use public IP's. In this case you should be able to get around the limitiation by attachiing a switch and dealing with routers and gateways manually. However, you cannot have the second NIC, even after completion of the migration.

However, the basic assumption with 2008 is you are using private IP addressing and a router.

Server 2008 std of course will support it.

The server is a Dell T410 that has 4 nic's actually. I can disable the 3 extra and run the setup again with the USB key, but I do not under stand your comment about attaching a switch.

The only nic that is attached to the network at all does go through a switch ATM .

Rob Williams

SBS 2008 has a few limitations that SBS 2003 did not have
1) It will ill only support 1 NIC, all others must be disabled, preferably in the BIOS, even after installation is complete.
2) During the set up of SBS 2008 it wants to 'see' a router, if it cannot find it you can configure it manually, but if it doesn't at least see a network connection it will not finish the installation. My suggestion was some folk have stated that attaching the SBS to a switch, with no router present, meets the requirement of 'seeing' a network and SBS completes installation and you can then configure it.

However re-reading I see #2 is not the primary concern at this point. My main point would be you stated "I assume after the successful migration I could change both ip's back to public", but you cannot have a second NIC on SBS 2008.
Assuming you can complete this bu using a private IP during set up, changing to public after completion, how are you going to protect the network with 1 NIC (no gateway capability) and no router.

2008 is definitely not designed for this configuration, though I appreciate your predicament.
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck

To add more info to the topic, the existing network is a 206.95.54.x with a subnet of It unfortunately is and was created by a legacy business system company that will not allow the range to be changed .

The existing server is and there is a router on .5 as well. There are approx 50 clients all hooked through multiple cisco switches.

I created the answer file with this exact info as well as the new server sbs2008 taking the ip address of

I had to install the drivers for the 4 BIC cards it did detect initially and after that, that is when I recieved the error about using public ip's .

I can disable all but one nic and it would be the one that will be hooked into one of the cisco switches.

There is most definitely a router in front of it between it and my isp provided fibre connection, so I am not worried about it routing or anything.

The router/firewall nat's the whole  network out to the actual real world ip's fine and all is good.

I am trying to migrate from the existing 2003 AD to the new SBS2008 and maintain the existing user and machine accounts instead of re doing the complete network that would take tons of extra work .

I have though about switching to a private ip schema to just do the migration and then back ,but I am sue that would create havoc as with dns and dhcp already on the public network.

Another though would be to switch the whole network private and then route to my business system network on the 206 via a dms off of my firewall . Not ideal , but i could manage.

Ultimately , I am looking for a way yo migrate with existing IP address of 206 .
Rob Williams

View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.

I am doing a mass change properly to a correct internal private address scheme and will work with the other vendor to have them change their equipment addressing as well.

Long and painful before I can start the migration again , but I do appreciate all feedback and award as well earned .

Not the answer I wanted, but it is the right answer

Rob Williams

Thanks Chris. Good luck with your project, I don't envy you.
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.