Combemartin
asked on
SBS2011 stuck on public IP
I have a 2003 server installed by some IT company over a decade ago, somehow they came up with this brilliant idea of using a public address for the internal network 200.200.200.xxx
I came across this server about 3 years ago, but by then, AD, DNS. ES are all already running, making matters worst, they also have Avaya IP phones and another bunch of IP related software installed.
I tried to fool the OS by changing the router IP back to a non-public IP, this allow the install stage through but then it can no longer find the old server name , kind of expected but I am desprate.
There are also around 40+ stations with a bunch of bespoke software that were installed on single user profile (not installed for All users).
I know I am asking for a miracle by the look of things, but is there anything I could try or a way to bypass the checks ?
Thanks as always.
I came across this server about 3 years ago, but by then, AD, DNS. ES are all already running, making matters worst, they also have Avaya IP phones and another bunch of IP related software installed.
I tried to fool the OS by changing the router IP back to a non-public IP, this allow the install stage through but then it can no longer find the old server name , kind of expected but I am desprate.
There are also around 40+ stations with a bunch of bespoke software that were installed on single user profile (not installed for All users).
I know I am asking for a miracle by the look of things, but is there anything I could try or a way to bypass the checks ?
Thanks as always.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
So are you trying to perform a migration?
Is the 2003 server SBS as well?
What is acting as the DHCP server, the router or the 2003 server?
Is the 2003 server SBS as well?
What is acting as the DHCP server, the router or the 2003 server?
ASKER
Hi,
I am hoping this to be a migration as I dont fancy rejoining 40+ stations as well as reinstalling their software on each machine.
The old server is a 2003 with Exchange 2003 (not SBS), and the new one is SBS2011
The router is DHCP.
Thank you.
I am hoping this to be a migration as I dont fancy rejoining 40+ stations as well as reinstalling their software on each machine.
The old server is a 2003 with Exchange 2003 (not SBS), and the new one is SBS2011
The router is DHCP.
Thank you.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi, I managed to changed the IP and updated DNS, build a second server, joined and migrated FSMO across and all seem ok.
Thank you all for all your help.
Thank you all for all your help.
That's great Combemartin well done!!
Thank you..
Thank you..
ASKER
Thank you for your post, I will try this in a few hours when I get to work.
One of my main concern is that even if I could sync and force the AD through, the fact that 2008 doesn't support public IP is a shadow on the installation, but I will give your suggestion a try first and see where it will take me.
Thank you.