Re: Changing IP addresses SBS 2000 Network

From: JeffM (jeffm_at_discussions.microsoft.com)
Date: 10/31/04 

Date: Sun, 31 Oct 2004 06:50:03 -0800

I am not only replacing the SBS 2000 server with an SBS 2003, I am also
replacing a very old Netscreen router with a SonicWall router. When I switch
the router to the new one the workstations have no problem getting on the
web, but the server can't.

I did change Wins, DNS, Subnetmask is correct, did not run the ICW however
since I don't see one in Windows SBS 2000.

Workstations have hard coded IP's an can ping the IP of the server, but not
the name of the server.

The fact the server can't even get on the web after the switch shows
something is quite screwy. When I change its iP back to the old one, and
switch back routers it works just fine on the web.

I did correctly set the server DNS, and put the DNS in the workstations as
well, pointing to both the server and the router IP. '

Pinging the server by name doesn't get a response.

I was resigning myself to having to switch the IP after I get done
installing the new server, I was just hoping to do it first so I didn't have
to change it when I was done installing the new one.

"Lanwench [MVP - Exchange]" wrote:

> JeffM wrote:
> > I have been trying to change the IP addresses for a SBS 2000 server
> > and the systems on the network. The problem is, the previous
> > consultant used a Public IP for the network address range, and I want
> > to move it over to the 192.168 range before installing an SBS 2003
> > server.
> >
> > Have a new Sonic Wall router setup for the 192.168.100.x ip range and
> > it is all configured correctly.
> >
> > When I replace the existing router with the Sonic wall
>
> Not sure what you mean -you have an existing Internet router/gateway device
> which you're leaving in place, right? So you're talking about replacing
> something else?
>
> > all the
> > workstations have no problem at all accessing the web or seeing each
> > other, but the SBS 2000 server won't connect to the web or see/be
> > seen by the other systems on the network.
> >
> > I have gone into the Server's network card settings (only one card)
> > and changed the IP to 192.168.100.100.
>
> And the DNS, and the default gateway? Subnet mask is correct?
>
> > Have then replaced the router
> > and the server could not be accessed. I then went into the DNS
> > settings and changed all the IP's for the domain right under the
> > Forward Look up zone, so that all systems are listed in the new range
> > including the server. Still the workstations can't see the server and
> > the server can't get on the web.
>
> After changing the IP on the server, make sure you fix your DNS on the
> server - make sure it's running right. Look in the DNS event logs for
> errors.
>
> Did you change your DHCP scope on the SBS server so all clients are picking
> up the new info? As in, DNS (SBS IP *only*), WINS (if you use it - also SBS
> IP, 0x8 for hybrid node), gateway (LAN IP of Sonicwall). I'm presuming your
> DNS suffix hasn't changed ;)
>
> On all client PCs, run ipconfig /release, ipconfig /renew, ipconfig
> /registerdns. You'll need to wait a bit til that works.
> >
> > Have added a Hosts line pointing to the server, on the workstations,
> > but the still can't see it on the network.
> >
> > I can ping the server from the workstations and they get a reply to
> > the server IP, they just can't access any files on it.
>
> When you pinged the server by name, what happened?
> If you got a reply, was it resolving via DNS or by broadcast? You can tell -
> if the reply comes from server.domain.local (or whatever), it's using DNS as
> it should be. If it's just from the name (server), it's broadcast, and your
> DNS isn't working right.
> >
> > I have moved IP ranges in the past on servers and had no problems,
> > but this SBS 2000 server just isn't acting right.
> >
> > I wanted to swap the IP range over to a private range before
> > installing a brand new server with SBS 2003, but I don't seem to be
> > getting very far.
> >
> > I know this SBS 2000 server was never setup right in the first place,
> > it works, but it is a mess. It was upgraded from SBS NT to 2000 and
> > had some real quirks, but has run ok for 2 years so I have avoided
> > changing anything until I had the new server ready to install.
> >
> > Anyone have a clue why I can't change this server over from it's
> > 90.x.x range to a 192.168.x.x range and get it to be seen on the
> > network.
>
>
>

Relevant Pages

  • Re: Cannot connect to RWW from home PC
    ... No 10.0.0.138 is the address used to log onto Thomson's router to make the ... On the DNS question I can add an MX record in the DNS area of GoDaddy's ... eth0 172.26.0.1/16 Extra none ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... NIC, you need to specify an external DNS server for DNS, instead of the ... Both NICs should point to his internal IP for DNS. ... forward ports to it reliably in the router. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot connect to RWW from home PC
    ... You say "And in the router you need to forward to your external nic IP" ... You say "You need the domain hoster to setup a DNS record that will be ... We have rerun CEICW sort of hoping it would sort out the router but no ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... The SBS DNS server, running on ... its IP it means that your problem is now DNS. ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... Even a single-NIC configuration should have ONLY the LAN IP of the server as ... Then you can run the CEICW or use the DNS console to enter ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
Loading