SBS 2000 & ICS setup questions

Hi all,

I have a couple of SBS 2000 & ICS questions.

1. What is the impact of changing the server's IP address
after SBS setup? Is there a tool to propogate the change
across all dependant services (like Novell's INETCFG)?

2. Do users need to login to the server to use the
Internet gateway? I am doing a phased install where some
users will remain on the old Novell/Sygate LAN for awhile,
and some will migrate to SBS right away. I would prefer to
use SBS for the Internet gateway for everyone.

Any Suggestions?

Best Regards ...... Craig

Chad
Tue Jul 29 17:02:57 CDT 2003

Hi Craig - see inline

--

Chad A. Gross

Lerman's Law of Technology: Any technical problem can be overcome
given enough time and money. Corollary: You are never given enough
time or money.


In news:069a01c35618$f43c6b30$a101280a@phx.gbl,
Craig Langley <calangley@sbcglobal.net> posted:
> Hi all,
>
> I have a couple of SBS 2000 & ICS questions.
>
> 1. What is the impact of changing the server's IP address
> after SBS setup? Is there a tool to propogate the change
> across all dependant services (like Novell's INETCFG)?

SBS2k doesn't have a built-in utility to change the IP. However, it is
pretty simple - just change the IP in your nic properties, then create a new
DHCP scope for the new address range (and disable the old scope), then
change the IP in DNS. Last, if you're using a static pool of IPs in RRAS
for remote clients, you'll want to update that as well.

>
> 2. Do users need to login to the server to use the
> Internet gateway? I am doing a phased install where some
> users will remain on the old Novell/Sygate LAN for awhile,
> and some will migrate to SBS right away. I would prefer to
> use SBS for the Internet gateway for everyone.

No problem. I'm assuming you're running ISA? If so, you'll need to create
a protocol rule that allows outbound traffic for any request. Then make
sure all of the machines have the internal IP of your SBS listed as their
default gateway and you should be good to go.

>
> Any Suggestions?
>
> Best Regards ...... Craig

Charlie
Tue Jul 29 22:01:01 CDT 2003

Don't forget about changing your DNS server entries on the network cards and
your ISA LAT. If you have web publishing or server publishing rules defined
in ISA, then you will need to change all of those to publish to the new
local IP address of the server.

--
Charlie Anthe
Microsoft Small Business Server Team

This posting is provided "AS IS" with no warranties, and confers no rights.

"Chad A Gross" <chad.gross@laytonflower.nospam.com> wrote in message
news:%23528s0hVDHA.1896@TK2MSFTNGP12.phx.gbl...
> Hi Craig - see inline
>
> --
>
> Chad A. Gross
>
> Lerman's Law of Technology: Any technical problem can be overcome
> given enough time and money. Corollary: You are never given enough
> time or money.
>
>
> In news:069a01c35618$f43c6b30$a101280a@phx.gbl,
> Craig Langley <calangley@sbcglobal.net> posted:
> > Hi all,
> >
> > I have a couple of SBS 2000 & ICS questions.
> >
> > 1. What is the impact of changing the server's IP address
> > after SBS setup? Is there a tool to propogate the change
> > across all dependant services (like Novell's INETCFG)?
>
> SBS2k doesn't have a built-in utility to change the IP. However, it is
> pretty simple - just change the IP in your nic properties, then create a
new
> DHCP scope for the new address range (and disable the old scope), then
> change the IP in DNS. Last, if you're using a static pool of IPs in RRAS
> for remote clients, you'll want to update that as well.
>
> >
> > 2. Do users need to login to the server to use the
> > Internet gateway? I am doing a phased install where some
> > users will remain on the old Novell/Sygate LAN for awhile,
> > and some will migrate to SBS right away. I would prefer to
> > use SBS for the Internet gateway for everyone.
>
> No problem. I'm assuming you're running ISA? If so, you'll need to
create
> a protocol rule that allows outbound traffic for any request. Then make
> sure all of the machines have the internal IP of your SBS listed as their
> default gateway and you should be good to go.
>
> >
> > Any Suggestions?
> >
> > Best Regards ...... Craig
>
>

Craig
Wed Jul 30 12:26:32 CDT 2003

Thanks for the reply, Chad!

In regard to question 2 below, do you have an example of a
protocol rule that I can use, or maybe a link that would
have some detailed info for rules and port mapping for,
say, PCAnywhere, etc?

Regards .... Craig

>-----Original Message-----
>Hi Craig - see inline
>
>--
>
>Chad A. Gross
>
>Lerman's Law of Technology: Any technical problem can be
overcome
>given enough time and money. Corollary: You are never
given enough
>time or money.
>
>
>In news:069a01c35618$f43c6b30$a101280a@phx.gbl,
>Craig Langley <calangley@sbcglobal.net> posted:
>> Hi all,
>>
>> I have a couple of SBS 2000 & ICS questions.
>>
>> 1. What is the impact of changing the server's IP
address
>> after SBS setup? Is there a tool to propogate the change
>> across all dependant services (like Novell's INETCFG)?
>
>SBS2k doesn't have a built-in utility to change the IP.
However, it is
>pretty simple - just change the IP in your nic
properties, then create a new
>DHCP scope for the new address range (and disable the old
scope), then
>change the IP in DNS. Last, if you're using a static
pool of IPs in RRAS
>for remote clients, you'll want to update that as well.
>
>>
>> 2. Do users need to login to the server to use the
>> Internet gateway? I am doing a phased install where some
>> users will remain on the old Novell/Sygate LAN for
awhile,
>> and some will migrate to SBS right away. I would prefer
to
>> use SBS for the Internet gateway for everyone.
>
>No problem. I'm assuming you're running ISA? If so,
you'll need to create
>a protocol rule that allows outbound traffic for any
request. Then make
>sure all of the machines have the internal IP of your SBS
listed as their
>default gateway and you should be good to go.
>
>>
>> Any Suggestions?
>>
>> Best Regards ...... Craig
>
>
>.
>

Chad
Wed Jul 30 16:47:18 CDT 2003

Hi Craig -

First, www.isaserver.org is a good reference.

Protocol Rules use the various protocols currently defined in ISA. ISA
comes with a decent number of pre-defined protocols. You can see these by
opening ISA Management and navigating to

Servers & Arrays
<servername>
Policy Elements
Protocol Definitions

If you need to allow outbound access for an app on client machines that uses
a port (protocol) not currently defined in ISA, you'll need to create a new
protocol definition (Action | New | Protocol Definition). You'll need to
know the protocol type (TCP / UDP / ICMP), the port number and the
direction. Most TCP protocols only need outbound access, while most UDP
protocols need Send/Receive). Once you've created your definition, you can
create a protocol rule based on this protocol. Navigate to

Servers & Arrays
<servername>
Access Policy
Protocol Rules

Action | New | Rule will start the new protocol rule wizard. Select the
protocol you want to use, apply the rule to Any Request (so that it can be
used by your Secure NAT clients still attached to the old Novell network)
and voila! There you go.

If you need to find port information for certain apps, usually a Google
Groups search with the app name and "ISA" in the search string will give you
the info you need pretty quickly . . .

--

Chad A. Gross

Lerman's Law of Technology: Any technical problem can be overcome
given enough time and money. Corollary: You are never given enough
time or money.


In news:0eec01c356bf$b85f4720$a601280a@phx.gbl,
Craig Langley <calangley@sbcglobal.net> posted:
> Thanks for the reply, Chad!
>
> In regard to question 2 below, do you have an example of a
> protocol rule that I can use, or maybe a link that would
> have some detailed info for rules and port mapping for,
> say, PCAnywhere, etc?
>
> Regards .... Craig
>
>> -----Original Message-----
>> Hi Craig - see inline
>>
>> --
>>
>> Chad A. Gross
>>
>> Lerman's Law of Technology: Any technical problem can be overcome
>> given enough time and money. Corollary: You are never given enough
>> time or money.
>>
>>
>> In news:069a01c35618$f43c6b30$a101280a@phx.gbl,
>> Craig Langley <calangley@sbcglobal.net> posted:
>>> Hi all,
>>>
>>> I have a couple of SBS 2000 & ICS questions.
>>>
>>> 1. What is the impact of changing the server's IP address
>>> after SBS setup? Is there a tool to propogate the change
>>> across all dependant services (like Novell's INETCFG)?
>>
>> SBS2k doesn't have a built-in utility to change the IP. However, it
>> is pretty simple - just change the IP in your nic properties, then
>> create a new DHCP scope for the new address range (and disable the
>> old scope), then change the IP in DNS. Last, if you're using a
>> static pool of IPs in RRAS for remote clients, you'll want to update
>> that as well.
>>
>>>
>>> 2. Do users need to login to the server to use the
>>> Internet gateway? I am doing a phased install where some
>>> users will remain on the old Novell/Sygate LAN for awhile,
>>> and some will migrate to SBS right away. I would prefer to
>>> use SBS for the Internet gateway for everyone.
>>
>> No problem. I'm assuming you're running ISA? If so, you'll need to
>> create a protocol rule that allows outbound traffic for any request.
>> Then make sure all of the machines have the internal IP of your SBS
>> listed as their default gateway and you should be good to go.
>>
>>>
>>> Any Suggestions?
>>>
>>> Best Regards ...... Craig
>>
>>
>> .

Craig
Wed Jul 30 18:28:51 CDT 2003

Hi Chad,

Thanks so much - that should help a lot!

Craig

>-----Original Message-----
>Hi Craig -
>
>First, www.isaserver.org is a good reference.
>
>Protocol Rules use the various protocols currently
defined in ISA. ISA
>comes with a decent number of pre-defined protocols. You
can see these by
>opening ISA Management and navigating to
>
>Servers & Arrays
> <servername>
> Policy Elements
> Protocol Definitions
>
>If you need to allow outbound access for an app on client
machines that uses
>a port (protocol) not currently defined in ISA, you'll
need to create a new
>protocol definition (Action | New | Protocol
Definition). You'll need to
>know the protocol type (TCP / UDP / ICMP), the port
number and the
>direction. Most TCP protocols only need outbound access,
while most UDP
>protocols need Send/Receive). Once you've created your
definition, you can
>create a protocol rule based on this protocol. Navigate
to
>
>Servers & Arrays
> <servername>
> Access Policy
> Protocol Rules
>
>Action | New | Rule will start the new protocol rule
wizard. Select the
>protocol you want to use, apply the rule to Any Request
(so that it can be
>used by your Secure NAT clients still attached to the old
Novell network)
>and voila! There you go.
>
>If you need to find port information for certain apps,
usually a Google
>Groups search with the app name and "ISA" in the search
string will give you
>the info you need pretty quickly . . .
>
>--
>
>Chad A. Gross
>
>Lerman's Law of Technology: Any technical problem can be
overcome
>given enough time and money. Corollary: You are never
given enough
>time or money.
>
>
>In news:0eec01c356bf$b85f4720$a601280a@phx.gbl,
>Craig Langley <calangley@sbcglobal.net> posted:
>> Thanks for the reply, Chad!
>>
>> In regard to question 2 below, do you have an example
of a
>> protocol rule that I can use, or maybe a link that would
>> have some detailed info for rules and port mapping for,
>> say, PCAnywhere, etc?
>>
>> Regards .... Craig
>>
>>> -----Original Message-----
>>> Hi Craig - see inline
>>>
>>> --
>>>
>>> Chad A. Gross
>>>
>>> Lerman's Law of Technology: Any technical problem can
be overcome
>>> given enough time and money. Corollary: You are never
given enough
>>> time or money.
>>>
>>>
>>> In news:069a01c35618$f43c6b30$a101280a@phx.gbl,
>>> Craig Langley <calangley@sbcglobal.net> posted:
>>>> Hi all,
>>>>
>>>> I have a couple of SBS 2000 & ICS questions.
>>>>
>>>> 1. What is the impact of changing the server's IP
address
>>>> after SBS setup? Is there a tool to propogate the
change
>>>> across all dependant services (like Novell's INETCFG)?
>>>
>>> SBS2k doesn't have a built-in utility to change the
IP. However, it
>>> is pretty simple - just change the IP in your nic
properties, then
>>> create a new DHCP scope for the new address range (and
disable the
>>> old scope), then change the IP in DNS. Last, if
you're using a
>>> static pool of IPs in RRAS for remote clients, you'll
want to update
>>> that as well.
>>>
>>>>
>>>> 2. Do users need to login to the server to use the
>>>> Internet gateway? I am doing a phased install where
some
>>>> users will remain on the old Novell/Sygate LAN for
awhile,
>>>> and some will migrate to SBS right away. I would
prefer to
>>>> use SBS for the Internet gateway for everyone.
>>>
>>> No problem. I'm assuming you're running ISA? If so,
you'll need to
>>> create a protocol rule that allows outbound traffic
for any request.
>>> Then make sure all of the machines have the internal
IP of your SBS
>>> listed as their default gateway and you should be good
to go.
>>>
>>>>
>>>> Any Suggestions?
>>>>
>>>> Best Regards ...... Craig
>>>
>>>
>>> .
>
>
>.
>

dabutler
Wed Jul 30 18:38:21 CDT 2003

Hi Chad,

Thank you for using Microsoft Technical Support Newsgroups.

In addition to the excellent suggestions given previously, make sure you
update the registry key listed in the following article:

284831 The ISA Server Control Service May Report Event 14158
http://support.microsoft.com/?id=284831

Once again, thank you for using the newsgroups.

Best Regards,



David Butler - MCSE NT4/2000
Microsoft Technical Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties,
and confers no rights.