Re: Changing ISP's



Hey Larry,

Well I went back and thought about this again and decided that I am making
this more difficult than it needs to be. Here is what I did...
I configured the linksys router to emulate the settings that the DSL
modem/router had and connected it to the network, ran the CEICW and entered
the new DNS address from the new ISP and all seems to be well. Both NIC's
are up and I can connect to the internet.

Now my question is; how do I properly enable DHCP on the server? Previously
DHCP was turned off and being provided by the DSL modem/router. Do I WANT to
enable DHCP on the server or just leave it disabled and go back and enable it
in the linksys?




"Larry Struckmeyer [SBS-MVP]" wrote:

The SBS internal nic and the external nics must be on different subnets.

In practical terms, this translates to the third octet in SBS Land, so I
often use:

Internal:
192.168.16.2
255.255.255.0

External:
192.168.61.2
255.255.255.0

and then set the LAN side of the router either at 61.1 or 61.254 for the
gateway.

In all cases, the DNS is 192.168.16.2 on every nic in the LAN, but of course
the SBS as DHCP server will give the workstations the correct settings after
you run the CEICW. Don't forget to turn off DHCP server on the
firewall/router.

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


"PWT24" <PWT24@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C9433B69-A98F-4215-B660-5E9E20BDA528@xxxxxxxxxxxxxxxx
Hi Larry,
Hopefully you get this since it is so far back on the newsgroup. If I
don't
hear from you soon I will have to repost as I am onsite now.

I am not 100% clear on my steps so here is the current configuration
WAN NIC
IP: 192.168.254.50
Sub: 255.255.255.0
Gateway: 192.168.254.254
DNS1: 192.168.254.3


LAN NIC
IP: 192.168.254.3
Sub: 255.255.255.0
Gateway: blank
DNS1: 192.168.254.3

From your explaination I understand to change the WAN NIC to something
like;
IP: 192.168.1.124
Sub: 255.255.255.0
Gateway: 192.168.1.1 (for now using a basic linksys wireless router)

Run the CEICW, Connect the router, change the LAN NIC by running the
change
server IP wizard, run the CEICW again.

Do I have this correct??




"Larry Struckmeyer [SBS-MVP]" wrote:

If most users are getting email there is no reason that I can see from
40K
feet to think ISA is at fault.

I suggest you go first just change the ip address on the SBS external nic
to
match the settings the new ISP gives you and run the CEICW and get that
to
work. Then install the edge device but leave ISA in place. Put the
settings given by the ISP on the WAN side of the edge device, change the
"external" nic and the LAN side of the edge device to be on a private
subnet
that is different from either the SBS or the WAN. Then forward the SBS
required ports to the ip address of the external nic.

Run the CEICW and set the all the ip addresses and the default email
address
for the email domain.

I would look at the SMTP properties of the user(s) who cannot receive
external mail..... I suspect the default email address is wrong. After
you
run the CEICW the default address should change to whatever you put in
the
CEICW, so look at those properties before and after you run the CEICW.

One more thing in your explanation that is strange. SMTP mail for
Exchange
will not be held anywhere, so a POP connector will not retrieve it. So
the
users that have Exchange SMTP mail and POP mail must have two different
email addresses, which is ok, unless you mean they are using the POP3
connector for Exchange, which is different that using an Outlook Pop
Connector.

In any case, as Merv suggests... run and fix the issues found by the SBS
BPA, check the event logs for other things you can fix, and use the
wizards.

Good luck... sounds like a challenging assignment. If you need any help,
please feel free to come back here (usually one thread per topic).

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


"PWT24" <PWT24@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3A9475FF-4DBE-422E-9E5E-83E0AA59CD73@xxxxxxxxxxxxxxxx
They don't have a firewall router. All they have is a DSL modem that
is
in
Bridge mode and ISA is handling the firewall functions. Again, this is
my
understanding since someone else setup this server for them.
However, yes I am going to provide them with one on the day we change
ISP's.

I thought I would remove ISA for a couple of reasons. First, this is a
company with 11 users who know absolutely nothing about computers let
alone
the server they have in place. Second, the staff member they recently
let
go
knew enough to be dangerous and that cost him his job. His answer to
everything was to just share drives and folders when he did not
understand
why someone could not see something on the network. I mean everything
from
C: drives on corporate officers workstations to most of the server. So
I
am
taking a small step in assuming that he probably messed with ISA and it
is
not configured properly anyway.

They have nothing but trouble with e-mail including 1 user who cannot
receive exchange mail. Everyone else can receive exchange mail but 1
user
has to rely on POP mail. I have changed his password, confirmed his
address,
removed his e-mail account in Outlook and reinstalled and still no
luck.

For some reason unknown to me there are 4 users with both POP and
Exchange
accounts on their workstations and the POP connector is not running on
the
server so I don't know why they even have them.

Just trying to clean up someone else's mess basically.



"Larry Struckmeyer [SBS-MVP]" wrote:

First part of your question has to do with what is between your SBS
and
the
ISP. If you have a firewall / router, the public IP at the WAN side
of
the
router must be changed, then run the CEICW to get the Public DNS
forwarders
set. Nothing else on your SBS will change.

If you don't have an edge firewall, get one. This is one of the
benefits
of
such a device.

Why remove ISA? It is a true firewall and causes no issues. But if
you
do
choose to remove it, you will have to get the edge firewall.

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


"PWT24" <PWT24@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6426DC9D-82FA-43E9-B060-51CB8F2F0485@xxxxxxxxxxxxxxxx
New customer with SBS2003 Standard and ISA and a 2 nic config will
be
changing ISP's from a DSL account to a Cable account. I know I will
need
to
run the CEICW to change the IP address to the new Static but are
there
any
"gotcha's" I need to look out for in regards to the e-mail accounts?

I would like to disable ISA and go to a one nic config are there any
doc's
on disabling ISA anywhere?

Thanks!






.



Relevant Pages

  • Re: RWW Timing
    ... If you have installed ISA, ... Expand the server node and highlight ''Monitoring''. ... In the following website you can find many useful resources related to SBS ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Help! w/ Upgrade-Installation problems with OMA/ActiveSync and
    ... Am I misinterpreting the summary doc from CEICW re: dhcp and dns settings ... under the SBS DNS forwarder tab. ... DNS server addresses I assume from the DSL modem. ...
    (microsoft.public.windows.server.sbs)
  • Re: DHCP Issues. Very strange
    ... default order of rule in ISA 2004. ... Windows SharePoint Services intranet site, ... server certificate on Web server name column and then click Next. ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS VPN setup?
    ... The 2-nic configuration is used when the SBS server will *also* act as your network's firewall. ... You purchase 2k3 PREMIUM and that comes with ISA to handle the firewall duties. ... To compare apples to apples, let us assume there is a network setup as I outlined above...and the firewall appliance is an ISA server, such as those available from Celestix. ...
    (microsoft.public.windows.server.sbs)
  • Re: CEICW and certificate FQDN
    ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... | Subject: Re: CEICW and certificate FQDN ... |> Server 2003, Premium Technologies ...
    (microsoft.public.windows.server.sbs)

Loading