I have started a migration from sbs 2003 to sbs 2008 premium. I have done
the basic load (everything up to starting the migration wizards on the new
server) so far and had one installation issue. The issue was that I could
not download updates.

When I try to run the CTIW it errors. Says that it cannot connect to the
internet. It cannot grab my router and make any changes (old router, not
upnp). However, my router is working fine with the 2003 server.

So, basically, no one on my network can connect to the internet and/or the
old exchange server. The new server cannot connect to the internet.
However, it does receive name resolution but will not ping.



I have turned off the firewall on the new server, just in case. I have not
installed anything whatsoever on the new server.

As far as I can tell, the new server is now acting as a DNS server as well
as the old one. If I change the DNS on my clients, they are able to connect
to the internet and the old server. If I change the DNS on the new server to
point to the old server, it still does not work and I believe that the SBS
2008 needs to point to itself anyway.

Regardless, it seems as though I have some type of a DNS issue on the new
SBS 2008 server and it has stalled my migration.

I thought that maybe I needed to do the CTIW from the migration wizard, but
that made no difference.

I have the ports on the router/firewall open, somewhat, they are redirected
to the old server.

I do not know if I have provided enough information.

Any assistance would be greatly appreciated.

SBS 2003 had one nic, no ISA.

The sbs 2008 server has 4 NICs, three are disabled.

"Cris Hanna [SBS - MVP]" wrote:

> Did the SBS 2003 have 2 nics or one? ISA?
> How many nics in the SBS 2008 server (active even if not attached to anything))
>
> --
> Cris Hanna [SBS - MVP] (since 1997)
> Co-Contributor, Windows Small Business Server 2008 Unleashed
> http://www.amazon.com/Windows-Small-...7269967&sr=8-1
> Owner, CPU Services, Belleville, IL
> A Microsoft Registered Partner
> ------------------------------------
> MVPs do not work for Microsoft
> Please do not submit questions directly to me.
>
> "ABCPoly-JRS" <ABCPolyJRS@newsgroup> wrote in message news:F036F70F-E398-47E3-B577-378E6989D19F@newsgroup
> I have started a migration from sbs 2003 to sbs 2008 premium. I have done
> the basic load (everything up to starting the migration wizards on the new
> server) so far and had one installation issue. The issue was that I could
> not download updates.
>
> When I try to run the CTIW it errors. Says that it cannot connect to the
> internet. It cannot grab my router and make any changes (old router, not
> upnp). However, my router is working fine with the 2003 server.
>
> So, basically, no one on my network can connect to the internet and/or the
> old exchange server. The new server cannot connect to the internet.
> However, it does receive name resolution but will not ping.
>
> I have turned off the firewall on the new server, just in case. I have not
> installed anything whatsoever on the new server.
>
> As far as I can tell, the new server is now acting as a DNS server as well
> as the old one. If I change the DNS on my clients, they are able to connect
> to the internet and the old server. If I change the DNS on the new server to
> point to the old server, it still does not work and I believe that the SBS
> 2008 needs to point to itself anyway.
>
> Regardless, it seems as though I have some type of a DNS issue on the new
> SBS 2008 server and it has stalled my migration.
>
> I thought that maybe I needed to do the CTIW from the migration wizard, but
> that made no difference.
>
> I have the ports on the router/firewall open, somewhat, they are redirected
> to the old server.
>
> I do not know if I have provided enough information.
>
> Any assistance would be greatly appreciated.

sbs2008 ip info:

ipv4 - 10.0.1.10 (Preferred)
S/N 255.255.255.0
GW 10.0.1.1
DNS 10.0.1.10 and 10.0.1.2
Netbios over TCPIP

10.0.1.10 is new server
10.0.1.1 is watchguard firewall
10.0.1.2 is existing sbs2003 svr

there is IPv6 info, as well, but didnt include it.

"Jim Behning SBS MVP" wrote:

> On every new SBS I have installed it says that it cannot configure the
> router. This is because I have not turned on that feature in the
> router. That has never prevented my SBS 2008 from connecting to the
> Internet. I have not done a migration yet but still the point is the
> wizard fusses about not being able to configure the router but that
> never causes a real problem.
>
> Post ipconfig/all from new server and workstation. I would assume that
> the new server should have its gateway pointing to your router ip.
>
> On Mon, 26 Apr 2010 05:01:01 -0700, ABCPoly-JRS
> <ABCPolyJRS@newsgroup> wrote:
>

> >I have started a migration from sbs 2003 to sbs 2008 premium. I have done
> >the basic load (everything up to starting the migration wizards on the new
> >server) so far and had one installation issue. The issue was that I could
> >not download updates.
> >
> >When I try to run the CTIW it errors. Says that it cannot connect to the
> >internet. It cannot grab my router and make any changes (old router, not
> >upnp). However, my router is working fine with the 2003 server.
> >
> >So, basically, no one on my network can connect to the internet and/or the
> >old exchange server. The new server cannot connect to the internet.
> >However, it does receive name resolution but will not ping.
> >
> >I have turned off the firewall on the new server, just in case. I have not
> >installed anything whatsoever on the new server.
> >
> >As far as I can tell, the new server is now acting as a DNS server as well
> >as the old one. If I change the DNS on my clients, they are able to connect
> >to the internet and the old server. If I change the DNS on the new server to
> >point to the old server, it still does not work and I believe that the SBS
> >2008 needs to point to itself anyway.
> >
> >Regardless, it seems as though I have some type of a DNS issue on the new
> >SBS 2008 server and it has stalled my migration.
> >
> >I thought that maybe I needed to do the CTIW from the migration wizard, but
> >that made no difference.
> >
> >I have the ports on the router/firewall open, somewhat, they are redirected
> >to the old server.
> >
> >I do not know if I have provided enough information.
> >
> >Any assistance would be greatly appreciated.

> See what SBS support is working on
> http://blogs.technet.com/sbs/default.aspx
> Check your SBS with the SBS Best Practices Analyzer
> http://blogs.technet.com/sbs/archive...A/default.aspx
> .
>

In article <080FA36D-0735-4BFD-95D9-5AF7BFCDA13E@newsgroup>,
ABCPolyJRS@newsgroup says...

>
> sbs2008 ip info:
>
> ipv4 - 10.0.1.10 (Preferred)
> S/N 255.255.255.0
> GW 10.0.1.1
> DNS 10.0.1.10 and 10.0.1.2
> Netbios over TCPIP
>
> 10.0.1.10 is new server
> 10.0.1.1 is watchguard firewall
> 10.0.1.2 is existing sbs2003 svr

None of your servers should point at the firewall for DNS.

The SBS box should point at itself for DNS.

If you want to resolve DNS between two different SBS domains, in the
network, setup a DNS forward to the OLD one from the new one, but the
new one should point at itself.

Never point at a external DNS on the NIC.


--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
spam999free@newsgroup (remove 999 for proper email address)

Actually, until the new SBS 2008 server has been joined to the domain and
the actual migration begins, it should point DNS to the old SBS server, not
itself. Once it is joined to the domain and AD enabled, then it should only
point to itself. (And you are absolutely correct - it should NEVER point to
an outside DNS, or to the router/firewall as a DNS server.)

Also, ensure that IPv6 is enabled on the SBS 2008 server or things will not
work correctly.

--
Charlie.
http://msmvps.com/blogs/russel




"Leythos" <spam999free@newsgroup> wrote in message
news:MPG.263f665d25ba5e0798a307@newsgroup

> In article <080FA36D-0735-4BFD-95D9-5AF7BFCDA13E@newsgroup>,
> ABCPolyJRS@newsgroup says...

>>
>> sbs2008 ip info:
>>
>> ipv4 - 10.0.1.10 (Preferred)
>> S/N 255.255.255.0
>> GW 10.0.1.1
>> DNS 10.0.1.10 and 10.0.1.2
>> Netbios over TCPIP
>>
>> 10.0.1.10 is new server
>> 10.0.1.1 is watchguard firewall
>> 10.0.1.2 is existing sbs2003 svr

>
> None of your servers should point at the firewall for DNS.
>
> The SBS box should point at itself for DNS.
>
> If you want to resolve DNS between two different SBS domains, in the
> network, setup a DNS forward to the OLD one from the new one, but the
> new one should point at itself.
>
> Never point at a external DNS on the NIC.
>
>
> --
> You can't trust your best friends, your five senses, only the little
> voice inside you that most civilians don't even hear -- Listen to that.
> Trust yourself.
> spam999free@newsgroup (remove 999 for proper email address)

Problem is resolved. I updated the firmware for the NICs and restarted.
Everything worked fine. Reran CTIW, everything passed.

Not sure if it was the reboot that fixed the issue or if it was the new
firmware.

Thanks to everyone for their responses, quick I might add, they are welcomed
and appreciated.

John


"Charlie Russel - MVP" wrote:

> Actually, until the new SBS 2008 server has been joined to the domain and
> the actual migration begins, it should point DNS to the old SBS server, not
> itself. Once it is joined to the domain and AD enabled, then it should only
> point to itself. (And you are absolutely correct - it should NEVER point to
> an outside DNS, or to the router/firewall as a DNS server.)
>
> Also, ensure that IPv6 is enabled on the SBS 2008 server or things will not
> work correctly.
>
> --
> Charlie.
> http://msmvps.com/blogs/russel
>
>
>
>
> "Leythos" <spam999free@newsgroup> wrote in message
> news:MPG.263f665d25ba5e0798a307@newsgroup

> > In article <080FA36D-0735-4BFD-95D9-5AF7BFCDA13E@newsgroup>,
> > ABCPolyJRS@newsgroup says...

> >>
> >> sbs2008 ip info:
> >>
> >> ipv4 - 10.0.1.10 (Preferred)
> >> S/N 255.255.255.0
> >> GW 10.0.1.1
> >> DNS 10.0.1.10 and 10.0.1.2
> >> Netbios over TCPIP
> >>
> >> 10.0.1.10 is new server
> >> 10.0.1.1 is watchguard firewall
> >> 10.0.1.2 is existing sbs2003 svr

> >
> > None of your servers should point at the firewall for DNS.
> >
> > The SBS box should point at itself for DNS.
> >
> > If you want to resolve DNS between two different SBS domains, in the
> > network, setup a DNS forward to the OLD one from the new one, but the
> > new one should point at itself.
> >
> > Never point at a external DNS on the NIC.
> >
> >
> > --
> > You can't trust your best friends, your five senses, only the little
> > voice inside you that most civilians don't even hear -- Listen to that.
> > Trust yourself.
> > spam999free@newsgroup (remove 999 for proper email address)

>
> .
>