• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 814
  • Last Modified:

SBS 2003 Changing Server IP address

After several years of letting the SBS2003 server poodle along, the time has come to update to SBS 2008 on a new server.

I've run the checks to ensure the Server is fit for the migration tool (I hope!) but need to change the network IP addresses and this is where I have a problem. The router was 192.168.0.10 and I changed it to 192.168.1.1 /255.255.255.0 as recommended.

The router continues to supply DCHP.

I changed my terminal to get its IP address from the router and changed the server IP address to 192.168.1.15/255.255.255.0. Initially I did this via the Control Panel.

My terminal can log on and Exchange works fine but but it will not allow me to connect to the KCSERVER domain and says I'm working off line.

Back on the server I've run the Internet Connection Wizard to ensure that the DNS values are correct (which they are), however when I accept that page of data I get an error message ".. the IP address of the router is not within the same address space (subnet) as the IP Address and subnet mask specified for the network adaptor..." Well they look OK to me!

I've rerun BPA and it now says the DNS client is not configured but when I run the link everything seems to be as it should be.

Any ideas what I should do?
0
Kinwardstone
Asked:
Kinwardstone
  • 6
  • 3
  • 3
3 Solutions
 
KinwardstoneAuthor Commented:
Oh, I forgot to mention that everything has been rebooted a couple of times :)
0
 
btdownloads7Commented:
On the server, I want to make sure that you still have a static IP set up. And also, what are the values for the IP address, subnet, gateway, and DNS server(s)?
0
 
KinwardstoneAuthor Commented:
Sorry for the delay

The Network card is set to a Static IP address (192.168.1.15 / 255.255.255.0).
Gateway 192.168.1.1
DNS is 192.168.1.15
WINS 192.168.1.15

the delay was caused by me finding that in the advanced options the card had a second IP address assigned (217.40.223.145 / 255.255.255.248). Goodness knows where this came from but it will have been there for 6 years. I removed it and re-ran the IC wizard and the error message has gone and it completes correctly. However, even after re-booting the server and clients I still cannot logon to the KCSERVER although Exchange continues to function.

I'm very confused!
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
btdownloads7Commented:
Then there has to be smething wrong with either the DNS settings on the server or the DHCP settings on the router (not assigning the correct DNS server to the clients).

Check what DNS server the clients are getting, and I'll bet that it's not 192.168.1.15. And if that's the case, the router has to be configured to have that as the DNS server, and should then assign it to clients. Also, run "ipconfig /flushdns" and then release/renew IP on each client to force it to get the correct settings.
0
 
KinwardstoneAuthor Commented:
The router settings are
IP Address 192.168.1.1 / 255.255.255.0
DHCP settings are 192.168.1.2 - 192.168.1.254

ipconfig /all on the client shows
IP address 192.168.1.2 / 255.255.255.0
default Gateway 192.168.1.1
DHCP Server 192.168.1.1
DNS Servers 192.168.1.15

It's a long time since I ran any of these DOS utilities so is thare any others I should try?
0
 
Rob WilliamsCommented:
With SBS 2003 you MUST use the change server IP wizard located under server management | Internet and e-mail. Not doing so will 'break' numerous services and can even result in a server rebuild. If you changed it within the NIC configuration running the change server IP wizard now with the same IP (the new one) 'usually' fixes the problem. When finished re-run the CEICW
0
 
btdownloads7Commented:
Well, all those settings look right, so it has to be a problem with the DNS server itself. I don't know what domain name you're using, but try pinging it (not the server name, but the local domain name) from both the server and the client PCs. Assuming that your local domain is "mydomain.local", the command is "ping mydomain.local". Check to see what IP address the clients are trying to connect to, and  if the pings are successful.
0
 
KinwardstoneAuthor Commented:
Hi guys

RobWill: I've ran the Change IP wizard then CEICW and rebooted the client but nothing has changed

btdownloads7: both (kinwardstone.local & KCSERVER) ping ok and show 192.168.1.15

Time for supper then some sleep I think! Any ideas for the morning?

(BTW thanks for the help so far!)
0
 
Rob WilliamsCommented:
SBS really should be your DHCP server. If the router is you must assign the SBS, and only the SBS as your DNS server. Do not allow the router or an ISP to be the alternate. Based on the information you provided above this is the case.
The router should also assign a WINS IP, that of the server. And, the one that is seldom done, the router should also assign the domain suffix, YourDomain.local, to the client. If the router doesn't have that capability add it on the connecting client under "use this DNS suffix for this connection" on the DNS tab of the advanced TCP/IP properties. It may be that this information was cached and is still linked to the old IP scheme.
0
 
KinwardstoneAuthor Commented:
Hi RobWill

I changed the router settings so it took DNS from 192.168.1.15 instead of the values supplied by the ISP. Also changed the TCP/IP properties. Rebooted everything - router/server/client but all to no avail!

Panic has set in as the network needs to be available for business tomorrow so I decided to return to the old set up and rethink my options. I changed the router back to 192.168.0.10 and the gateway to 192.168.0.15. I used the "change server IP" wizard and reset it back to 192.168.0.15 then, as it requests, ran CEIC wizard. I changed the client's TCP/IP gateway details and rebooted it. Amazingly, everything sprang back into life and the old network is fully up and running (Phew!)

When I ran one of the server's wizards it asked to confirm that the ISP DNS addresses were correct - I take it that this is the correct and only place the ISP's DNS addresses should be? If not then at least everything is working again!

So where do I go from here? I should've initially run the CSIP wizard instead of manually changing the TCP/IP settings but re-running it later should've fixed any underlying issue.

As time (and disk space) is short, I think I'll leave the network as it is and attempt a manual transfer of the Exchange data to the new 2008 server (if that's possible). There is little else of value on the server which is dependant on 2003/8.

Thanks for you help.
0
 
Rob WilliamsCommented:
>>" I take it that this is the correct and only place the ISP's DNS addresses should be?"
Correct.
In a Windows Domain, not just an SBS network, The server and clients MUST point ONLY to your internal DNS servers, in this case the SBS, for DNS. You cannot add a router or ISP as an alternate. The ISP's are added as forwarders to the DNS management console. In the case of SBS the CEICW does this for you as per your comment above.

You shouldn't need to change to a 192.168.1.0/24 for the migration, it just needs to be a 192.168.x.x/24 subnet. If you only have a few users you might want to do a manual move to SBS 2008, but why not SBS 2011?  However if doing so you have to remove clients from the existing domain, manually recreate all user accounts, export e-mail to pst files and re-import.

An alternative is a migration kit from http://www.sbsmigration.com/ for about $200. Their method allows you to do a slow controlled migration from which you can revert back to your original configuration at any point, they have better documentation and some tools, and they offer 90 days unlimited support.

I would also recommend moving DHCP from the router to your server before migrating or changing the IP if you plan to do so. From an earlier post of mine:

It is very critical the server be your DHCP server, and if it is not, the wizards will fail, and the best practices analyzer will warn you of this. This is not just true of SBS but it is best to have any Windows server as the DHCP server for the following reasons:
-allows for more scope options than your router can offer. Some of which are necessary for SBS services
-secure dynamic DNS updates
-Proper DNS registration for older O/S clients
-central management
-DHCP integration for VPN clients
-eliminates the risk of the router automatically assigning the ISP's DNS, resulting is slow name resolution

If the server is off line you will lose internet access. However fact is in a Windows domain regardless of whether you use the server or the router for DHCP the only DNS servers you can assign to your DHCP clients is your internal DNS servers. If you assign the router or ISP as even an alternate, you will have slow logons, name resolution issues, and the http://connect wizard for joining clients to the SBS will fail. The only way to retain internet when the SBS is of line is to add a second DC/DNS server to your domain.

#1 rule of Windows DNS, server and clients must point ONLY to the internal DNS server. ISP's DNS is added as a forwarder.

Ignoring best practices, I have never understood if the SBS is offline and you have lost file access, authentication, and e-mail (Exchange), why is internet so important. That is just a personal feeling.

Having said all of that it is not compulsory to use the SBS for DHCP, but if not you should read the following:
http://sbs.seandaniel.com/2008/10/do-i-absolutely-have-to-run-dhcp-on-sbs.html
0
 
KinwardstoneAuthor Commented:
The help offered was good and unearthed some deficiencies in the network setup but the lack of time prevented the real cause of the problem from being discovered.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 6
  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now