Afternoon All,



I am in the process of changing my default gateway on my SBS from
10.10.0.254 to 10.10.0.222. When I change the default gateway all DNS seems
to stop working and since it is the DNS for our network nobody can get to the
net. I have tried manually changing the gateway as well as the wizard but
they both didnt work for me.

If I take one of my LAN clients and configure its settings to the .222
gateway with an DNS of 4.2.2.2 the client works just fine. The only problem
that I have is that I cannot get the SBS to do the same. If I configure a
secondary DNS into my SBS of 4.2.2.2 and a default gateway of .222 I can only
ping out to IP addresses.

-- I am thinking about setting up a second DNS on one of my servers and
using it for testing on my .222 gateway or using it as the DNS while I
configure the SBS.

-- Also it seems as though my users login scripts have stopped working once
we changed the gateway. I have this error as well as some DNS server errors
in my log.

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5706
Date: 10/6/2009
Time: 5:49:07 PM
User: N/A
Computer: MCSVR01
Description:
The Netlogon service could not create server share
C:\WINDOWS\SYSVOL\sysvol\mccoysales.local\SCRIPTS. The following error
occurred:
Access is denied.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 05 00 00 00 ....

The problem is even after changing the settings back to .254 which is the
original gateway and rebooting the Sysvol refuses to run any scripts for my
users.

Any thoughts would be Appreciated .. and Thanks1

Noncentz--

SBS 2000, 2003 or 2008?

What do you have for your DNS Forwarders on the DNS admin tool? I'm
guessing you have the .254, but you should really have your ISPs DNS
servers there.


Jim

On Wed, 7 Oct 2009 11:45:01 -0700, Noncentz
<Noncentz@newsgroup> wrote:

>Afternoon All,
>
>I am in the process of changing my default gateway on my SBS from
>10.10.0.254 to 10.10.0.222. When I change the default gateway all DNS seems
>to stop working and since it is the DNS for our network nobody can get to the
>net. I have tried manually changing the gateway as well as the wizard but
>they both didnt work for me.
>
>If I take one of my LAN clients and configure its settings to the .222
>gateway with an DNS of 4.2.2.2 the client works just fine. The only problem
>that I have is that I cannot get the SBS to do the same. If I configure a
>secondary DNS into my SBS of 4.2.2.2 and a default gateway of .222 I can only
>ping out to IP addresses.
>
>-- I am thinking about setting up a second DNS on one of my servers and
>using it for testing on my .222 gateway or using it as the DNS while I
>configure the SBS.
>
>-- Also it seems as though my users login scripts have stopped working once
>we changed the gateway. I have this error as well as some DNS server errors
>in my log.
>
>Event Type: Error
>Event Source: NETLOGON
>Event Category: None
>Event ID: 5706
>Date: 10/6/2009
>Time: 5:49:07 PM
>User: N/A
>Computer: MCSVR01
>Description:
>The Netlogon service could not create server share
>C:\WINDOWS\SYSVOL\sysvol\mccoysales.local\SCRIPTS. The following error
>occurred:
>Access is denied.
>
>For more information, see Help and Support Center at
>http://go.microsoft.com/fwlink/events.asp.
>Data:
>0000: 05 00 00 00 ....
>
>The problem is even after changing the settings back to .254 which is the
>original gateway and rebooting the Sysvol refuses to run any scripts for my
>users.
>
>Any thoughts would be Appreciated .. and Thanks1
>
>Noncentz--

Hi Noncentz,

The best way is to run the CEICW (configure email and internet connection
wizard) to change the setting. Use the SBS Management console.

--
-----------------------------------------------
Les Connor [SBS MVP]

"Noncentz" <Noncentz@newsgroup> wrote in message
news:B08A8791-C18E-4123-8B34-180EC668076D@newsgroup

> Afternoon All,
>
> I am in the process of changing my default gateway on my SBS from
> 10.10.0.254 to 10.10.0.222. When I change the default gateway all DNS
> seems
> to stop working and since it is the DNS for our network nobody can get to
> the
> net. I have tried manually changing the gateway as well as the wizard but
> they both didnt work for me.
>
> If I take one of my LAN clients and configure its settings to the .222
> gateway with an DNS of 4.2.2.2 the client works just fine. The only
> problem
> that I have is that I cannot get the SBS to do the same. If I configure a
> secondary DNS into my SBS of 4.2.2.2 and a default gateway of .222 I can
> only
> ping out to IP addresses.
>
> -- I am thinking about setting up a second DNS on one of my servers and
> using it for testing on my .222 gateway or using it as the DNS while I
> configure the SBS.
>
> -- Also it seems as though my users login scripts have stopped working
> once
> we changed the gateway. I have this error as well as some DNS server
> errors
> in my log.
>
> Event Type: Error
> Event Source: NETLOGON
> Event Category: None
> Event ID: 5706
> Date: 10/6/2009
> Time: 5:49:07 PM
> User: N/A
> Computer: MCSVR01
> Description:
> The Netlogon service could not create server share
> C:\WINDOWS\SYSVOL\sysvol\mccoysales.local\SCRIPTS. The following error
> occurred:
> Access is denied.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 05 00 00 00 ....
>
> The problem is even after changing the settings back to .254 which is the
> original gateway and rebooting the Sysvol refuses to run any scripts for
> my
> users.
>
> Any thoughts would be Appreciated .. and Thanks1
>
> Noncentz--

I ran dnsdiag and Here is what I have for my DNS information. From what I can
see my forwarders consist of 2 public DNS servers. Given this is on .254
because it is during working hours.

Starting test: DNS
Test results for domain controllers:

DC: mcsvr01.mccoysales.local
Domain: mccoysales.local


TEST: Authentication (Auth)
Authentication test: Successfully completed

TEST: Basic (Basc)
Microsoft(R) Windows(R) Server 2003 for Small Business
Server (Service Pack level: 2.0) is supported
NETLOGON service is running
kdc service is running
DNSCACHE service is running
DNS service is running
DC is a DNS server
Network adapters information:
Adapter [00000009] Intel(R) Advanced Network Services
Virtual Adapter:
MAC address is 00:14:22:21:5F:F3
IP address is static
IP address: 10.10.0.1
DNS servers:
10.10.0.1 (mcsvr01.mccoysales.local.) [Valid]
The A record for this DC was found
The SOA record for the Active Directory zone was found
The Active Directory zone on this DC/DNS server was found
(primary)
Root zone on this DC/DNS server was not found

TEST: Forwarders/Root hints (Forw)
Recursion is enabled
Forwarders Information:
208.67.222.222 (<name unavailable>) [Valid]
4.2.2.2 (<name unavailable>) [Valid]

TEST: Delegations (Del)
Delegation information for the zone: mccoysales.local.
Delegated domain name: _msdcs.mccoysales.local.
DNS server: mcsvr01.mccoysales.local. IP:10.10.0.1
[Valid]

TEST: Dynamic update (Dyn)
Dynamic update is enabled on the zone mccoysales.local.
Test record _dcdiag_test_record added successfully in zone
mccoysales.local.
Test record _dcdiag_test_record deleted successfully in
zone mccoysales.local.

TEST: Records registration (RReg)
Network Adapter [00000009] Intel(R) Advanced Network
Services Virtual Adapter:
Matching A record found at DNS server 10.10.0.1:
mcsvr01.mccoysales.local

Matching CNAME record found at DNS server 10.10.0.1:

d3769285-d81e-40ca-907e-fa37df6c28f1._msdcs.mccoysales.local

Matching DC SRV record found at DNS server 10.10.0.1:
_ldap._tcp.dc._msdcs.mccoysales.local

Matching GC SRV record found at DNS server 10.10.0.1:
_ldap._tcp.gc._msdcs.mccoysales.local

Matching PDC SRV record found at DNS server 10.10.0.1:
_ldap._tcp.pdc._msdcs.mccoysales.local


Summary of test results for DNS servers used by the above domain
controllers:

DNS server: 10.10.0.1 (mcsvr01.mccoysales.local.)
All tests passed on this DNS server
This is a valid DNS server
Name resolution is funtional. _ldap._tcp SRV record for the
forest root domain is registered
Delegation to the domain _msdcs.mccoysales.local. is
operational

DNS server: 208.67.222.222 (<name unavailable>)
All tests passed on this DNS server
This is a valid DNS server

DNS server: 4.2.2.2 (<name unavailable>)
All tests passed on this DNS server
This is a valid DNS server

Summary of DNS test results:

Auth Basc Forw Del Dyn RReg
Ext

________________________________________________________________
Domain: mccoysales.local
mcsvr01 PASS PASS PASS PASS PASS PASS
n/a

......................... mccoysales.local passed test DNS


"Jim" wrote:

> SBS 2000, 2003 or 2008?
>
> What do you have for your DNS Forwarders on the DNS admin tool? I'm
> guessing you have the .254, but you should really have your ISPs DNS
> servers there.
>
>
> Jim
>
> On Wed, 7 Oct 2009 11:45:01 -0700, Noncentz
> <Noncentz@newsgroup> wrote:
>

> >Afternoon All,
> >
> >I am in the process of changing my default gateway on my SBS from
> >10.10.0.254 to 10.10.0.222. When I change the default gateway all DNS seems
> >to stop working and since it is the DNS for our network nobody can get to the
> >net. I have tried manually changing the gateway as well as the wizard but
> >they both didnt work for me.
> >
> >If I take one of my LAN clients and configure its settings to the .222
> >gateway with an DNS of 4.2.2.2 the client works just fine. The only problem
> >that I have is that I cannot get the SBS to do the same. If I configure a
> >secondary DNS into my SBS of 4.2.2.2 and a default gateway of .222 I can only
> >ping out to IP addresses.
> >
> >-- I am thinking about setting up a second DNS on one of my servers and
> >using it for testing on my .222 gateway or using it as the DNS while I
> >configure the SBS.
> >
> >-- Also it seems as though my users login scripts have stopped working once
> >we changed the gateway. I have this error as well as some DNS server errors
> >in my log.
> >
> >Event Type: Error
> >Event Source: NETLOGON
> >Event Category: None
> >Event ID: 5706
> >Date: 10/6/2009
> >Time: 5:49:07 PM
> >User: N/A
> >Computer: MCSVR01
> >Description:
> >The Netlogon service could not create server share
> >C:\WINDOWS\SYSVOL\sysvol\mccoysales.local\SCRIPTS. The following error
> >occurred:
> >Access is denied.
> >
> >For more information, see Help and Support Center at
> >http://go.microsoft.com/fwlink/events.asp.
> >Data:
> >0000: 05 00 00 00 ....
> >
> >The problem is even after changing the settings back to .254 which is the
> >original gateway and rebooting the Sysvol refuses to run any scripts for my
> >users.
> >
> >Any thoughts would be Appreciated .. and Thanks1
> >
> >Noncentz--

>

Oh also SBS 2003 R2

"Jim" wrote:

> SBS 2000, 2003 or 2008?
>
> What do you have for your DNS Forwarders on the DNS admin tool? I'm
> guessing you have the .254, but you should really have your ISPs DNS
> servers there.
>
>
> Jim
>
> On Wed, 7 Oct 2009 11:45:01 -0700, Noncentz
> <Noncentz@newsgroup> wrote:
>

> >Afternoon All,
> >
> >I am in the process of changing my default gateway on my SBS from
> >10.10.0.254 to 10.10.0.222. When I change the default gateway all DNS seems
> >to stop working and since it is the DNS for our network nobody can get to the
> >net. I have tried manually changing the gateway as well as the wizard but
> >they both didnt work for me.
> >
> >If I take one of my LAN clients and configure its settings to the .222
> >gateway with an DNS of 4.2.2.2 the client works just fine. The only problem
> >that I have is that I cannot get the SBS to do the same. If I configure a
> >secondary DNS into my SBS of 4.2.2.2 and a default gateway of .222 I can only
> >ping out to IP addresses.
> >
> >-- I am thinking about setting up a second DNS on one of my servers and
> >using it for testing on my .222 gateway or using it as the DNS while I
> >configure the SBS.
> >
> >-- Also it seems as though my users login scripts have stopped working once
> >we changed the gateway. I have this error as well as some DNS server errors
> >in my log.
> >
> >Event Type: Error
> >Event Source: NETLOGON
> >Event Category: None
> >Event ID: 5706
> >Date: 10/6/2009
> >Time: 5:49:07 PM
> >User: N/A
> >Computer: MCSVR01
> >Description:
> >The Netlogon service could not create server share
> >C:\WINDOWS\SYSVOL\sysvol\mccoysales.local\SCRIPTS. The following error
> >occurred:
> >Access is denied.
> >
> >For more information, see Help and Support Center at
> >http://go.microsoft.com/fwlink/events.asp.
> >Data:
> >0000: 05 00 00 00 ....
> >
> >The problem is even after changing the settings back to .254 which is the
> >original gateway and rebooting the Sysvol refuses to run any scripts for my
> >users.
> >
> >Any thoughts would be Appreciated .. and Thanks1
> >
> >Noncentz--

>

Les,

At first I though this would be the case and I ran CEICW via the To do List.
When I ran the wizard I choose broadband and changed the default Gateway to
..222. After the wizard completed (we just choose to leave everything else as
is) we were not able to access DNS from the SBS. We were able to ip IP
though.

Funny thing is I changed the DG manually and it did not change in the
wizard? I assume the wizard is doing a bit more than I am by just changing
the DG.

DNS server: 10.10.0.1 (mcsvr01.mccoysales.local.)
All tests passed on this DNS server
This is a valid DNS server
Name resolution is funtional. _ldap._tcp SRV record for the
forest root domain is registered
Delegation to the domain _msdcs.mccoysales.local. is
operational

DNS server: 208.67.222.222 (<name unavailable>)
All tests passed on this DNS server
This is a valid DNS server

DNS server: 4.2.2.2 (<name unavailable>)
All tests passed on this DNS server
This is a valid DNS server

"Les Connor [SBS MVP]" wrote:

> Hi Noncentz,
>
> The best way is to run the CEICW (configure email and internet connection
> wizard) to change the setting. Use the SBS Management console.
>
> --
> -----------------------------------------------
> Les Connor [SBS MVP]
>
> "Noncentz" <Noncentz@newsgroup> wrote in message
> news:B08A8791-C18E-4123-8B34-180EC668076D@newsgroup

> > Afternoon All,
> >
> > I am in the process of changing my default gateway on my SBS from
> > 10.10.0.254 to 10.10.0.222. When I change the default gateway all DNS
> > seems
> > to stop working and since it is the DNS for our network nobody can get to
> > the
> > net. I have tried manually changing the gateway as well as the wizard but
> > they both didnt work for me.
> >
> > If I take one of my LAN clients and configure its settings to the .222
> > gateway with an DNS of 4.2.2.2 the client works just fine. The only
> > problem
> > that I have is that I cannot get the SBS to do the same. If I configure a
> > secondary DNS into my SBS of 4.2.2.2 and a default gateway of .222 I can
> > only
> > ping out to IP addresses.
> >
> > -- I am thinking about setting up a second DNS on one of my servers and
> > using it for testing on my .222 gateway or using it as the DNS while I
> > configure the SBS.
> >
> > -- Also it seems as though my users login scripts have stopped working
> > once
> > we changed the gateway. I have this error as well as some DNS server
> > errors
> > in my log.
> >
> > Event Type: Error
> > Event Source: NETLOGON
> > Event Category: None
> > Event ID: 5706
> > Date: 10/6/2009
> > Time: 5:49:07 PM
> > User: N/A
> > Computer: MCSVR01
> > Description:
> > The Netlogon service could not create server share
> > C:\WINDOWS\SYSVOL\sysvol\mccoysales.local\SCRIPTS. The following error
> > occurred:
> > Access is denied.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> > Data:
> > 0000: 05 00 00 00 ....
> >
> > The problem is even after changing the settings back to .254 which is the
> > original gateway and rebooting the Sysvol refuses to run any scripts for
> > my
> > users.
> >
> > Any thoughts would be Appreciated .. and Thanks1
> >
> > Noncentz--

>
>

Can you explain what the goal is? Do you have one nic or two in the SBS
2003? What/where is the .222 address, and why? From the server can you
ping the GW address, and can you ping the public DNS servers, and if so, can
you ping yahoo.com?

A default gateway is nothing more than the information that is used to find
address that don't exist in the ip range that the request can "see".
Normally this would be .1 or .254, but there is nothing magic about these
numbers. If the nic is on the same subnet as the gateway device and you ask
for 71.08.44.32, for example, and your sub net is different anywhere in the
first three octaves, the request should be sent to the GW, and if the
forwarders, router and public DNS servers are doing their job, and the
requested url/ip is available you should be good to go.

So, given that the .254 is just a number, and it was (I assume) all working,
why the change?

--
Larry
Please post the resolution to your
issue so that others may benefit.

Get a Health Check for SBS at:
www.sbsbpa.com


"Noncentz" <Noncentz@newsgroup> wrote in message
news30A53CF-0258-4599-8396-D7A6ABE6D797@newsgroup

> Les,
>
> At first I though this would be the case and I ran CEICW via the To do
> List.
> When I ran the wizard I choose broadband and changed the default Gateway
> to
> .222. After the wizard completed (we just choose to leave everything else
> as
> is) we were not able to access DNS from the SBS. We were able to ip IP
> though.
>
> Funny thing is I changed the DG manually and it did not change in the
> wizard? I assume the wizard is doing a bit more than I am by just changing
> the DG.
>
> DNS server: 10.10.0.1 (mcsvr01.mccoysales.local.)
> All tests passed on this DNS server
> This is a valid DNS server
> Name resolution is funtional. _ldap._tcp SRV record for the
> forest root domain is registered
> Delegation to the domain _msdcs.mccoysales.local. is
> operational
>
> DNS server: 208.67.222.222 (<name unavailable>)
> All tests passed on this DNS server
> This is a valid DNS server
>
> DNS server: 4.2.2.2 (<name unavailable>)
> All tests passed on this DNS server
> This is a valid DNS server
>
> "Les Connor [SBS MVP]" wrote:
>

>> Hi Noncentz,
>>
>> The best way is to run the CEICW (configure email and internet connection
>> wizard) to change the setting. Use the SBS Management console.
>>
>> --
>> -----------------------------------------------
>> Les Connor [SBS MVP]
>>
>> "Noncentz" <Noncentz@newsgroup> wrote in message
>> news:B08A8791-C18E-4123-8B34-180EC668076D@newsgroup

>> > Afternoon All,
>> >
>> > I am in the process of changing my default gateway on my SBS from
>> > 10.10.0.254 to 10.10.0.222. When I change the default gateway all DNS
>> > seems
>> > to stop working and since it is the DNS for our network nobody can get
>> > to
>> > the
>> > net. I have tried manually changing the gateway as well as the wizard
>> > but
>> > they both didnt work for me.
>> >
>> > If I take one of my LAN clients and configure its settings to the .222
>> > gateway with an DNS of 4.2.2.2 the client works just fine. The only
>> > problem
>> > that I have is that I cannot get the SBS to do the same. If I configure
>> > a
>> > secondary DNS into my SBS of 4.2.2.2 and a default gateway of .222 I
>> > can
>> > only
>> > ping out to IP addresses.
>> >
>> > -- I am thinking about setting up a second DNS on one of my servers and
>> > using it for testing on my .222 gateway or using it as the DNS while I
>> > configure the SBS.
>> >
>> > -- Also it seems as though my users login scripts have stopped working
>> > once
>> > we changed the gateway. I have this error as well as some DNS server
>> > errors
>> > in my log.
>> >
>> > Event Type: Error
>> > Event Source: NETLOGON
>> > Event Category: None
>> > Event ID: 5706
>> > Date: 10/6/2009
>> > Time: 5:49:07 PM
>> > User: N/A
>> > Computer: MCSVR01
>> > Description:
>> > The Netlogon service could not create server share
>> > C:\WINDOWS\SYSVOL\sysvol\mccoysales.local\SCRIPTS. The following error
>> > occurred:
>> > Access is denied.
>> >
>> > For more information, see Help and Support Center at
>> > http://go.microsoft.com/fwlink/events.asp.
>> > Data:
>> > 0000: 05 00 00 00 ....
>> >
>> > The problem is even after changing the settings back to .254 which is
>> > the
>> > original gateway and rebooting the Sysvol refuses to run any scripts
>> > for
>> > my
>> > users.
>> >
>> > Any thoughts would be Appreciated .. and Thanks1
>> >
>> > Noncentz--

>>
>>

Sure,

We have 2 NIC running as a team on our SBS. The reasoning behind the move is
that we are upgrading our network from Frame to MPLS.

Currently our frame network uses .254 as its gateway. So we setup a new MPLS
router which also connects to the internet and gave it the address of .222.
We would like all of the clients and servers to use this new MPLS internet
connetion and phase out the Frame router. See the frame router will
eventually be "No More" and the .222 router will be our locations only
connection to the internet.

My assumption was that changing the DG would not effect DNS because the
forwarders are set to 4.2.2.2 and 208.67.222.222 which have nothing to do
with anything on the internal LAN. When we switch the DG over to .222 though
DNS just fails to forward to these public DNS servers. I can ping the
servers.. I can ping the any external ip... I just cant ping google.com using
a naming convention.


"Larry Struckmeyer [SBS-MVP]" wrote:

> Can you explain what the goal is? Do you have one nic or two in the SBS
> 2003? What/where is the .222 address, and why? From the server can you
> ping the GW address, and can you ping the public DNS servers, and if so, can
> you ping yahoo.com?
>
> A default gateway is nothing more than the information that is used to find
> address that don't exist in the ip range that the request can "see".
> Normally this would be .1 or .254, but there is nothing magic about these
> numbers. If the nic is on the same subnet as the gateway device and you ask
> for 71.08.44.32, for example, and your sub net is different anywhere in the
> first three octaves, the request should be sent to the GW, and if the
> forwarders, router and public DNS servers are doing their job, and the
> requested url/ip is available you should be good to go.
>
> So, given that the .254 is just a number, and it was (I assume) all working,
> why the change?
>
> --
> Larry
> Please post the resolution to your
> issue so that others may benefit.
>
> Get a Health Check for SBS at:
> www.sbsbpa.com
>
>
> "Noncentz" <Noncentz@newsgroup> wrote in message
> news30A53CF-0258-4599-8396-D7A6ABE6D797@newsgroup

> > Les,
> >
> > At first I though this would be the case and I ran CEICW via the To do
> > List.
> > When I ran the wizard I choose broadband and changed the default Gateway
> > to
> > .222. After the wizard completed (we just choose to leave everything else
> > as
> > is) we were not able to access DNS from the SBS. We were able to ip IP
> > though.
> >
> > Funny thing is I changed the DG manually and it did not change in the
> > wizard? I assume the wizard is doing a bit more than I am by just changing
> > the DG.
> >
> > DNS server: 10.10.0.1 (mcsvr01.mccoysales.local.)
> > All tests passed on this DNS server
> > This is a valid DNS server
> > Name resolution is funtional. _ldap._tcp SRV record for the
> > forest root domain is registered
> > Delegation to the domain _msdcs.mccoysales.local. is
> > operational
> >
> > DNS server: 208.67.222.222 (<name unavailable>)
> > All tests passed on this DNS server
> > This is a valid DNS server
> >
> > DNS server: 4.2.2.2 (<name unavailable>)
> > All tests passed on this DNS server
> > This is a valid DNS server
> >
> > "Les Connor [SBS MVP]" wrote:
> >

> >> Hi Noncentz,
> >>
> >> The best way is to run the CEICW (configure email and internet connection
> >> wizard) to change the setting. Use the SBS Management console.
> >>
> >> --
> >> -----------------------------------------------
> >> Les Connor [SBS MVP]
> >>
> >> "Noncentz" <Noncentz@newsgroup> wrote in message
> >> news:B08A8791-C18E-4123-8B34-180EC668076D@newsgroup
> >> > Afternoon All,
> >> >
> >> > I am in the process of changing my default gateway on my SBS from
> >> > 10.10.0.254 to 10.10.0.222. When I change the default gateway all DNS
> >> > seems
> >> > to stop working and since it is the DNS for our network nobody can get
> >> > to
> >> > the
> >> > net. I have tried manually changing the gateway as well as the wizard
> >> > but
> >> > they both didnt work for me.
> >> >
> >> > If I take one of my LAN clients and configure its settings to the .222
> >> > gateway with an DNS of 4.2.2.2 the client works just fine. The only
> >> > problem
> >> > that I have is that I cannot get the SBS to do the same. If I configure
> >> > a
> >> > secondary DNS into my SBS of 4.2.2.2 and a default gateway of .222 I
> >> > can
> >> > only
> >> > ping out to IP addresses.
> >> >
> >> > -- I am thinking about setting up a second DNS on one of my servers and
> >> > using it for testing on my .222 gateway or using it as the DNS while I
> >> > configure the SBS.
> >> >
> >> > -- Also it seems as though my users login scripts have stopped working
> >> > once
> >> > we changed the gateway. I have this error as well as some DNS server
> >> > errors
> >> > in my log.
> >> >
> >> > Event Type: Error
> >> > Event Source: NETLOGON
> >> > Event Category: None
> >> > Event ID: 5706
> >> > Date: 10/6/2009
> >> > Time: 5:49:07 PM
> >> > User: N/A
> >> > Computer: MCSVR01
> >> > Description:
> >> > The Netlogon service could not create server share
> >> > C:\WINDOWS\SYSVOL\sysvol\mccoysales.local\SCRIPTS. The following error
> >> > occurred:
> >> > Access is denied.
> >> >
> >> > For more information, see Help and Support Center at
> >> > http://go.microsoft.com/fwlink/events.asp.
> >> > Data:
> >> > 0000: 05 00 00 00 ....
> >> >
> >> > The problem is even after changing the settings back to .254 which is
> >> > the
> >> > original gateway and rebooting the Sysvol refuses to run any scripts
> >> > for
> >> > my
> >> > users.
> >> >
> >> > Any thoughts would be Appreciated .. and Thanks1
> >> >
> >> > Noncentz--
> >>
> >>

>
>

Two things, maybe three. I admit I am out of my depth here, so I am suggesting
ideas that will either prompt you to consider this from a different point
of view, or encourage others who know better to jump in and correct me, in
which case I will have learned something, which is most of the goal for my
being in this space. If I did not already have a signature line and an identity
here, I would sign this "puzzled". <g>

First, not sure that "phase out" and "default" belong in the same paragraph,
let alone the same sentence. Default is default, so it seems it should be
one of the other. Not picking on your choice of words, here, just hoping
you mean to "stop" not "phase out" using .254. This means that the carrier
for the new circut has to be finished provisioning "your" circut and all
of the settings and connection on their end.

Second, if I read you correctly you have 2 NICS teamed on the same subnet
and all computers, including the SBS are attached to a switch, along with
the router. Can you help me understand the benefits of this, and have you
tried disabling one of the nics and then running the CEICW?

Third, the *kind* of service offered by the carrier should have nothing to
do with the ip settings on the ports of your devices, although it may introduce
some complexity into the relationship between the LAN and the WAN, with devices
to facilitate the hand off that I have never seen. However, a Gateway, as
commonly used is the exit point of your LAN, and then there should be (afaik)
some translation device (NAT router, Firewall, etc.) between your LAN and
the WAN.

If I understand this correctly, the GW does not need to be changed, just
the ip on the WAN side of the edge device (assuming it has changed) to meet
the requirements of the carrier so that the tranlation has somewhere to go
once it "routes" out of the LAN and into the LAN. If you have two edge devices
and are switching between them, perhaps you could use .254 on one and .253
on the other. The change from .254 down to .222 seems strange.

In any case, unless your network has some conflict with the .222 address
on "your" side of the edge device, once you key that number into its LAN
side and run the CEICW, you should be good to go. Did you say you could
ping the 10.10.0.222 address once it was in the LAN side of the router?

Fourth, and one you can only determine by speaking to the carrier, is it
possible that the DNS servers they are wanting you to use *must* be used
on their network?

Fifth: When you run the CEICW with the settings the new ISP gave you, do
you get any errors on screen or in the event viewer?

And finally, i think. Can you post up the results of ipconfig /all > c:\iptest.txt
from a workstation and the server, and provide the ip settings for both sides
of the edge device. Perhaps one that works, probably the .254 setting, and
one that does not work, the .222 setting. Those could be separate posts.,
and please don't change the ip numbers, although you could alter the internal
names so long as you were consistant.


-
Larry
Please post the resolution to your
issue so others may benefit
-
Get Your SBS Health Check at
www.sbsbpa.com

> Sure,
>
> We have 2 NIC running as a team on our SBS. The reasoning behind the
> move is that we are upgrading our network from Frame to MPLS.
>
> Currently our frame network uses .254 as its gateway. So we setup a
> new MPLS router which also connects to the internet and gave it the
> address of .222. We would like all of the clients and servers to use
> this new MPLS internet connetion and phase out the Frame router. See
> the frame router will eventually be "No More" and the .222 router will
> be our locations only connection to the internet.
>
> My assumption was that changing the DG would not effect DNS because
> the forwarders are set to 4.2.2.2 and 208.67.222.222 which have
> nothing to do with anything on the internal LAN. When we switch the DG
> over to .222 though DNS just fails to forward to these public DNS
> servers. I can ping the servers.. I can ping the any external ip... I
> just cant ping google.com using a naming convention.
>
> "Larry Struckmeyer [SBS-MVP]" wrote:
>

>> Can you explain what the goal is? Do you have one nic or two in the
>> SBS 2003? What/where is the .222 address, and why? From the server
>> can you ping the GW address, and can you ping the public DNS servers,
>> and if so, can you ping yahoo.com?
>>
>> A default gateway is nothing more than the information that is used
>> to find address that don't exist in the ip range that the request can
>> "see". Normally this would be .1 or .254, but there is nothing magic
>> about these numbers. If the nic is on the same subnet as the gateway
>> device and you ask for 71.08.44.32, for example, and your sub net is
>> different anywhere in the first three octaves, the request should be
>> sent to the GW, and if the forwarders, router and public DNS servers
>> are doing their job, and the requested url/ip is available you should
>> be good to go.
>>
>> So, given that the .254 is just a number, and it was (I assume) all
>> working, why the change?
>>
>> --
>> Larry
>> Please post the resolution to your
>> issue so that others may benefit.
>> Get a Health Check for SBS at:
>> www.sbsbpa.com
>> "Noncentz" <Noncentz@newsgroup> wrote in message
>> news30A53CF-0258-4599-8396-D7A6ABE6D797@newsgroup
>>

>>> Les,
>>>
>>> At first I though this would be the case and I ran CEICW via the To
>>> do
>>> List.
>>> When I ran the wizard I choose broadband and changed the default
>>> Gateway
>>> to
>>> .222. After the wizard completed (we just choose to leave everything
>>> else
>>> as
>>> is) we were not able to access DNS from the SBS. We were able to ip
>>> IP
>>> though.
>>> Funny thing is I changed the DG manually and it did not change in
>>> the wizard? I assume the wizard is doing a bit more than I am by
>>> just changing the DG.
>>>
>>> DNS server: 10.10.0.1 (mcsvr01.mccoysales.local.)
>>> All tests passed on this DNS server
>>> This is a valid DNS server
>>> Name resolution is funtional. _ldap._tcp SRV record for the
>>> forest root domain is registered
>>> Delegation to the domain _msdcs.mccoysales.local. is
>>> operational
>>> DNS server: 208.67.222.222 (<name unavailable>)
>>> All tests passed on this DNS server
>>> This is a valid DNS server
>>> DNS server: 4.2.2.2 (<name unavailable>)
>>> All tests passed on this DNS server
>>> This is a valid DNS server
>>> "Les Connor [SBS MVP]" wrote:
>>>
>>>> Hi Noncentz,
>>>>
>>>> The best way is to run the CEICW (configure email and internet
>>>> connection wizard) to change the setting. Use the SBS Management
>>>> console.
>>>>
>>>> --
>>>> -----------------------------------------------
>>>> Les Connor [SBS MVP]
>>>> "Noncentz" <Noncentz@newsgroup> wrote in message
>>>> news:B08A8791-C18E-4123-8B34-180EC668076D@newsgroup
>>>>
>>>>> Afternoon All,
>>>>>
>>>>> I am in the process of changing my default gateway on my SBS from
>>>>> 10.10.0.254 to 10.10.0.222. When I change the default gateway all
>>>>> DNS
>>>>> seems
>>>>> to stop working and since it is the DNS for our network nobody can
>>>>> get
>>>>> to
>>>>> the
>>>>> net. I have tried manually changing the gateway as well as the
>>>>> wizard
>>>>> but
>>>>> they both didnt work for me.
>>>>> If I take one of my LAN clients and configure its settings to the
>>>>> .222
>>>>> gateway with an DNS of 4.2.2.2 the client works just fine. The
>>>>> only
>>>>> problem
>>>>> that I have is that I cannot get the SBS to do the same. If I
>>>>> configure
>>>>> a
>>>>> secondary DNS into my SBS of 4.2.2.2 and a default gateway of .222
>>>>> I
>>>>> can
>>>>> only
>>>>> ping out to IP addresses.
>>>>> -- I am thinking about setting up a second DNS on one of my
>>>>> servers and using it for testing on my .222 gateway or using it as
>>>>> the DNS while I configure the SBS.
>>>>>
>>>>> -- Also it seems as though my users login scripts have stopped
>>>>> working
>>>>> once
>>>>> we changed the gateway. I have this error as well as some DNS
>>>>> server
>>>>> errors
>>>>> in my log.
>>>>> Event Type: Error
>>>>> Event Source: NETLOGON
>>>>> Event Category: None
>>>>> Event ID: 5706
>>>>> Date: 10/6/2009
>>>>> Time: 5:49:07 PM
>>>>> User: N/A
>>>>> Computer: MCSVR01
>>>>> Description:
>>>>> The Netlogon service could not create server share
>>>>> C:\WINDOWS\SYSVOL\sysvol\mccoysales.local\SCRIPTS. The following
>>>>> error
>>>>> occurred:
>>>>> Access is denied.
>>>>> For more information, see Help and Support Center at
>>>>> http://go.microsoft.com/fwlink/events.asp.
>>>>> Data:
>>>>> 0000: 05 00 00 00 ....
>>>>> The problem is even after changing the settings back to .254 which
>>>>> is
>>>>> the
>>>>> original gateway and rebooting the Sysvol refuses to run any
>>>>> scripts
>>>>> for
>>>>> my
>>>>> users.
>>>>> Any thoughts would be Appreciated .. and Thanks1
>>>>>
>>>>> Noncentz--
>>>>>

"Larry Struckmeyer[SBS-MVP]" <lstruckmeyer@newsgroup-wizards.com> wrote in message
news:4e68351540c28cc1595c3099a51@newsgroup

I agree that I can't see how the WAN side of the router would have anything
to do with the internal network, the LAN side of the router. Unless Noncentz
is saying that the folks changed the internal LAN IP of the router to .222.
If that is the case, change it to whatever gateway it was previously instead
of goung through the hassle of changing on the internal machines.

I also thought that the ISP's router would be connected to some other
firewall/router internally. Some ISP routers can be set up as bridged, to
allow the internal firewall to be used to control traffic where it's WAN
side is bridged to allow the firewall to use the external WAN IP on its WAN
interface. If not bridgeable, it complicates matters with an additional
subnet and a static route on the ISP's router will be required between the
ISP's router and an internal router. But from the description provided by
Noncents, I'm not sure if an internal firewall exists, and if it doesn't,
this paragraph is moot.

So from what I see, based on what I've read (unless I missed something?),
simply changing the internal LAN IP to the previous router will suffice.

Ace

> Two things, maybe three. I admit I am out of my depth here, so I am
> suggesting ideas that will either prompt you to consider this from a
> different point of view, or encourage others who know better to jump in
> and correct me, in which case I will have learned something, which is most
> of the goal for my being in this space. If I did not already have a
> signature line and an identity here, I would sign this "puzzled". <g>
>
> First, not sure that "phase out" and "default" belong in the same
> paragraph, let alone the same sentence. Default is default, so it seems
> it should be one of the other. Not picking on your choice of words, here,
> just hoping you mean to "stop" not "phase out" using .254. This means
> that the carrier for the new circut has to be finished provisioning "your"
> circut and all of the settings and connection on their end.
>
> Second, if I read you correctly you have 2 NICS teamed on the same subnet
> and all computers, including the SBS are attached to a switch, along with
> the router. Can you help me understand the benefits of this, and have you
> tried disabling one of the nics and then running the CEICW?
>
> Third, the *kind* of service offered by the carrier should have nothing to
> do with the ip settings on the ports of your devices, although it may
> introduce some complexity into the relationship between the LAN and the
> WAN, with devices to facilitate the hand off that I have never seen.
> However, a Gateway, as commonly used is the exit point of your LAN, and
> then there should be (afaik) some translation device (NAT router,
> Firewall, etc.) between your LAN and the WAN.
>
> If I understand this correctly, the GW does not need to be changed, just
> the ip on the WAN side of the edge device (assuming it has changed) to
> meet the requirements of the carrier so that the tranlation has somewhere
> to go once it "routes" out of the LAN and into the LAN. If you have two
> edge devices and are switching between them, perhaps you could use .254 on
> one and .253 on the other. The change from .254 down to .222 seems
> strange.
>
> In any case, unless your network has some conflict with the .222 address
> on "your" side of the edge device, once you key that number into its LAN
> side and run the CEICW, you should be good to go. Did you say you could
> ping the 10.10.0.222 address once it was in the LAN side of the router?
>
> Fourth, and one you can only determine by speaking to the carrier, is it
> possible that the DNS servers they are wanting you to use *must* be used
> on their network?
> Fifth: When you run the CEICW with the settings the new ISP gave you, do
> you get any errors on screen or in the event viewer?
>
> And finally, i think. Can you post up the results of ipconfig /all >
> c:\iptest.txt from a workstation and the server, and provide the ip
> settings for both sides of the edge device. Perhaps one that works,
> probably the .254 setting, and one that does not work, the .222 setting.
> Those could be separate posts., and please don't change the ip numbers,
> although you could alter the internal names so long as you were
> consistant.
>
>
> -
> Larry
> Please post the resolution to your
> issue so others may benefit
> -
> Get Your SBS Health Check at
> www.sbsbpa.com
>
>

>> Sure,
>>
>> We have 2 NIC running as a team on our SBS. The reasoning behind the
>> move is that we are upgrading our network from Frame to MPLS.
>>
>> Currently our frame network uses .254 as its gateway. So we setup a
>> new MPLS router which also connects to the internet and gave it the
>> address of .222. We would like all of the clients and servers to use
>> this new MPLS internet connetion and phase out the Frame router. See
>> the frame router will eventually be "No More" and the .222 router will
>> be our locations only connection to the internet.
>>
>> My assumption was that changing the DG would not effect DNS because
>> the forwarders are set to 4.2.2.2 and 208.67.222.222 which have
>> nothing to do with anything on the internal LAN. When we switch the DG
>> over to .222 though DNS just fails to forward to these public DNS
>> servers. I can ping the servers.. I can ping the any external ip... I
>> just cant ping google.com using a naming convention.
>>
>> "Larry Struckmeyer [SBS-MVP]" wrote:
>>

>>> Can you explain what the goal is? Do you have one nic or two in the
>>> SBS 2003? What/where is the .222 address, and why? From the server
>>> can you ping the GW address, and can you ping the public DNS servers,
>>> and if so, can you ping yahoo.com?
>>>
>>> A default gateway is nothing more than the information that is used
>>> to find address that don't exist in the ip range that the request can
>>> "see". Normally this would be .1 or .254, but there is nothing magic
>>> about these numbers. If the nic is on the same subnet as the gateway
>>> device and you ask for 71.08.44.32, for example, and your sub net is
>>> different anywhere in the first three octaves, the request should be
>>> sent to the GW, and if the forwarders, router and public DNS servers
>>> are doing their job, and the requested url/ip is available you should
>>> be good to go.
>>>
>>> So, given that the .254 is just a number, and it was (I assume) all
>>> working, why the change?
>>>
>>> --
>>> Larry
>>> Please post the resolution to your
>>> issue so that others may benefit.
>>> Get a Health Check for SBS at:
>>> www.sbsbpa.com
>>> "Noncentz" <Noncentz@newsgroup> wrote in message
>>> news30A53CF-0258-4599-8396-D7A6ABE6D797@newsgroup
>>>
>>>> Les,
>>>>
>>>> At first I though this would be the case and I ran CEICW via the To
>>>> do
>>>> List.
>>>> When I ran the wizard I choose broadband and changed the default
>>>> Gateway
>>>> to
>>>> .222. After the wizard completed (we just choose to leave everything
>>>> else
>>>> as
>>>> is) we were not able to access DNS from the SBS. We were able to ip
>>>> IP
>>>> though.
>>>> Funny thing is I changed the DG manually and it did not change in
>>>> the wizard? I assume the wizard is doing a bit more than I am by
>>>> just changing the DG.
>>>>
>>>> DNS server: 10.10.0.1 (mcsvr01.mccoysales.local.)
>>>> All tests passed on this DNS server
>>>> This is a valid DNS server
>>>> Name resolution is funtional. _ldap._tcp SRV record for the
>>>> forest root domain is registered
>>>> Delegation to the domain _msdcs.mccoysales.local. is
>>>> operational
>>>> DNS server: 208.67.222.222 (<name unavailable>)
>>>> All tests passed on this DNS server
>>>> This is a valid DNS server
>>>> DNS server: 4.2.2.2 (<name unavailable>)
>>>> All tests passed on this DNS server
>>>> This is a valid DNS server
>>>> "Les Connor [SBS MVP]" wrote:
>>>>
>>>>> Hi Noncentz,
>>>>>
>>>>> The best way is to run the CEICW (configure email and internet
>>>>> connection wizard) to change the setting. Use the SBS Management
>>>>> console.
>>>>>
>>>>> --
>>>>> -----------------------------------------------
>>>>> Les Connor [SBS MVP]
>>>>> "Noncentz" <Noncentz@newsgroup> wrote in message
>>>>> news:B08A8791-C18E-4123-8B34-180EC668076D@newsgroup
>>>>>
>>>>>> Afternoon All,
>>>>>>
>>>>>> I am in the process of changing my default gateway on my SBS from
>>>>>> 10.10.0.254 to 10.10.0.222. When I change the default gateway all
>>>>>> DNS
>>>>>> seems
>>>>>> to stop working and since it is the DNS for our network nobody can
>>>>>> get
>>>>>> to
>>>>>> the
>>>>>> net. I have tried manually changing the gateway as well as the
>>>>>> wizard
>>>>>> but
>>>>>> they both didnt work for me.
>>>>>> If I take one of my LAN clients and configure its settings to the
>>>>>> .222
>>>>>> gateway with an DNS of 4.2.2.2 the client works just fine. The
>>>>>> only
>>>>>> problem
>>>>>> that I have is that I cannot get the SBS to do the same. If I
>>>>>> configure
>>>>>> a
>>>>>> secondary DNS into my SBS of 4.2.2.2 and a default gateway of .222
>>>>>> I
>>>>>> can
>>>>>> only
>>>>>> ping out to IP addresses.
>>>>>> -- I am thinking about setting up a second DNS on one of my
>>>>>> servers and using it for testing on my .222 gateway or using it as
>>>>>> the DNS while I configure the SBS.
>>>>>>
>>>>>> -- Also it seems as though my users login scripts have stopped
>>>>>> working
>>>>>> once
>>>>>> we changed the gateway. I have this error as well as some DNS
>>>>>> server
>>>>>> errors
>>>>>> in my log.
>>>>>> Event Type: Error
>>>>>> Event Source: NETLOGON
>>>>>> Event Category: None
>>>>>> Event ID: 5706
>>>>>> Date: 10/6/2009
>>>>>> Time: 5:49:07 PM
>>>>>> User: N/A
>>>>>> Computer: MCSVR01
>>>>>> Description:
>>>>>> The Netlogon service could not create server share
>>>>>> C:\WINDOWS\SYSVOL\sysvol\mccoysales.local\SCRIPTS. The following
>>>>>> error
>>>>>> occurred:
>>>>>> Access is denied.
>>>>>> For more information, see Help and Support Center at
>>>>>> http://go.microsoft.com/fwlink/events.asp.
>>>>>> Data:
>>>>>> 0000: 05 00 00 00 ....
>>>>>> The problem is even after changing the settings back to .254 which
>>>>>> is
>>>>>> the
>>>>>> original gateway and rebooting the Sysvol refuses to run any
>>>>>> scripts
>>>>>> for
>>>>>> my
>>>>>> users.
>>>>>> Any thoughts would be Appreciated .. and Thanks1
>>>>>>
>>>>>> Noncentz--
>>>>>>

>
>