Suddenly I have two machines with the same problem.....

Both machines are COMPLETELY different in hardware.

The one machine is NEW (P4, 2,4Ghz 1024mb) IDE on promise4000 Raid1 120GB
The other is dual P3 900 1024ECC ScSi 80GB (raid1)

Both run SBS2000 Servicepack3
Both run Mcafee AV
The last machine already for over 2 years without a hassle....

I just moved the second machine and put it to a new ROUTED SUBNET Internet
Access. (it was behind a router with a DMZ)
The other one is ALSO on a routed subnet.....

I ran the ICW using two NICS.
The one nic is connected to a switch for the INTERNAL network, the other
directly to the Router.
The only checked thing with the second Nic is TCP/IP
Binding order is: Internal / External / RAS
The external nic's DNS is the servers internal IP-address.

The problem on BOTH machines:

Exchange, although set to start automatic..... does NOT start
Drive M is NOT created.
There is a truckload of error messages..

RPC not started (with the older machine)
ILS not starting (hangs)


Until 20.00 when it was on the old router.... no problem.... restart and
run.
NOW, on routed subnet.... ONLY trouble...
Could this routed subnet cause the problems?

Harpert

Re: two machines, same problem, Exchange Drive M by Jeff

Jeff
Fri Sep 19 17:04:25 CDT 2003

Did I follow correctly from your post that you change the IP of the primary
nic on an SBS?

When you do this, you will need to revise many other things, including the
DHCP, DNS, WINS, perhaps RRAS configuration as well. Here's some
information I put together
Changing the IP with SBS 2000


There's no problem with changing the IP, though it's enough of a hassle that
you usually would want to avoid doing it if you can. I'm going to post a
list things to look for, but not detailed instructions. If you have a
problem, post back the specifics of what you need:

(these are approximately the order I would address it too)

Primary NIC IP
DNS on the Primary NIC
Any static entries in the WINS/DNS tab on the primary NIC

DHCP Server Scope
WINS Server database refresh (probably delete the entire contents)
RRAS DHCP Scope if you have entries listed there

DNS Zones
DNS Reverse Lookups
Flush and restart the DNS entries

(if any used)
HOSTS
LMHOSTS
Static Routes, if any

I think these are all fixed with the Internet Connection Wizard, but check:
Exchange
IIS Configuration of default website locations and bindings
ISA Defaults
ISA Custom Rules
ISA Client configuration if IP was specified for the configuration target

Shutdown and restart. Check for errors.

At each client station, release and renew IP
Check for static entries in WINS/DNS




Re: two machines, same problem, Exchange Drive M by harpert

harpert
Fri Sep 19 17:43:33 CDT 2003

Dear Jeff,

No (ofcourse) I did NOT change the IPaddress of the internal adapter.

I just changed the INTERNET connection from a simple router with Internal
IPaddress 192.168.1.1 connected to the servers external NIC (ip
192.168.1.10)
The router was set to DMZ.

NOW the server is connected to Internet using ROUTED subnet (Versatel)
This means you get a simple router and 8 IPaddresses.
Actually you can only use 5 of them.
As an example:

The IpAddresses are as follows:
11.22.33.120 (used by versatel)
11.22.33.121 (used by the router (gateway))
11.22.33.122
11.22.33.123
11.22.33.124
11.22.33.125
11.22.33.126
11.22.33.127 (used by Versatel)

I connected the server (external NIC) to this router using a switch.
I set the IPAddress to:
11.22.33.125
gateway to:
11.22.33.121
DNS to the servers internal IPaddress:
10.0.0.3

I ran the ICW.....
Told the ICW I want to use 2 nics
Point to the IP address of the router: (11.22.33.121)
And to the public DNS of Versatel: 62.58.62.132

I restarted the SBS and...... everything ran stuck.....
NO drive M
NO start of exchange
No start of RPC...

I now disconnected the External Nic from the router.
Restarted and waited untill I could connect to the server using TS on a
laptop on the Internal NIC using a second switch.

NOW there was NO problem....
Afterwards I reconnected the external nic to the router...
And... everything works FINE....

This is a complete riddle to me...............

Harpert

dleton [SBS-MVP]" <jeff@cfisolutions.com> schreef in bericht
news:uXql9lvfDHA.1700@TK2MSFTNGP10.phx.gbl...
> Did I follow correctly from your post that you change the IP of the
primary
> nic on an SBS?
>
> When you do this, you will need to revise many other things, including the
> DHCP, DNS, WINS, perhaps RRAS configuration as well. Here's some
> information I put together
> Changing the IP with SBS 2000
>
>
> There's no problem with changing the IP, though it's enough of a hassle
that
> you usually would want to avoid doing it if you can. I'm going to post a
> list things to look for, but not detailed instructions. If you have a
> problem, post back the specifics of what you need:
>
> (these are approximately the order I would address it too)
>
> Primary NIC IP
> DNS on the Primary NIC
> Any static entries in the WINS/DNS tab on the primary NIC
>
> DHCP Server Scope
> WINS Server database refresh (probably delete the entire contents)
> RRAS DHCP Scope if you have entries listed there
>
> DNS Zones
> DNS Reverse Lookups
> Flush and restart the DNS entries
>
> (if any used)
> HOSTS
> LMHOSTS
> Static Routes, if any
>
> I think these are all fixed with the Internet Connection Wizard, but
check:
> Exchange
> IIS Configuration of default website locations and bindings
> ISA Defaults
> ISA Custom Rules
> ISA Client configuration if IP was specified for the configuration target
>
> Shutdown and restart. Check for errors.
>
> At each client station, release and renew IP
> Check for static entries in WINS/DNS
>
>
>



Re: two machines, same problem, Exchange Drive M by Jeff

Jeff
Fri Sep 19 18:09:26 CDT 2003

So is the issue that you can't reboot with the NIC attached to the router or
that it happened just the one time and not again?

"harpert" <nomail@mail.com> wrote in message
news:#LV9S#vfDHA.1752@TK2MSFTNGP10.phx.gbl...
> Dear Jeff,
>
> No (ofcourse) I did NOT change the IPaddress of the internal adapter.
>
> I just changed the INTERNET connection from a simple router with Internal
> IPaddress 192.168.1.1 connected to the servers external NIC (ip
> 192.168.1.10)
> The router was set to DMZ.
>
> NOW the server is connected to Internet using ROUTED subnet (Versatel)
> This means you get a simple router and 8 IPaddresses.
> Actually you can only use 5 of them.
> As an example:
>
> The IpAddresses are as follows:
> 11.22.33.120 (used by versatel)
> 11.22.33.121 (used by the router (gateway))
> 11.22.33.122
> 11.22.33.123
> 11.22.33.124
> 11.22.33.125
> 11.22.33.126
> 11.22.33.127 (used by Versatel)
>
> I connected the server (external NIC) to this router using a switch.
> I set the IPAddress to:
> 11.22.33.125
> gateway to:
> 11.22.33.121
> DNS to the servers internal IPaddress:
> 10.0.0.3
>
> I ran the ICW.....
> Told the ICW I want to use 2 nics
> Point to the IP address of the router: (11.22.33.121)
> And to the public DNS of Versatel: 62.58.62.132
>
> I restarted the SBS and...... everything ran stuck.....
> NO drive M
> NO start of exchange
> No start of RPC...
>
> I now disconnected the External Nic from the router.
> Restarted and waited untill I could connect to the server using TS on a
> laptop on the Internal NIC using a second switch.
>
> NOW there was NO problem....
> Afterwards I reconnected the external nic to the router...
> And... everything works FINE....
>
> This is a complete riddle to me...............
>
> Harpert
>
> dleton [SBS-MVP]" <jeff@cfisolutions.com> schreef in bericht
> news:uXql9lvfDHA.1700@TK2MSFTNGP10.phx.gbl...
> > Did I follow correctly from your post that you change the IP of the
> primary
> > nic on an SBS?
> >
> > When you do this, you will need to revise many other things, including
the
> > DHCP, DNS, WINS, perhaps RRAS configuration as well. Here's some
> > information I put together
> > Changing the IP with SBS 2000
> >
> >
> > There's no problem with changing the IP, though it's enough of a hassle
> that
> > you usually would want to avoid doing it if you can. I'm going to post
a
> > list things to look for, but not detailed instructions. If you have a
> > problem, post back the specifics of what you need:
> >
> > (these are approximately the order I would address it too)
> >
> > Primary NIC IP
> > DNS on the Primary NIC
> > Any static entries in the WINS/DNS tab on the primary NIC
> >
> > DHCP Server Scope
> > WINS Server database refresh (probably delete the entire contents)
> > RRAS DHCP Scope if you have entries listed there
> >
> > DNS Zones
> > DNS Reverse Lookups
> > Flush and restart the DNS entries
> >
> > (if any used)
> > HOSTS
> > LMHOSTS
> > Static Routes, if any
> >
> > I think these are all fixed with the Internet Connection Wizard, but
> check:
> > Exchange
> > IIS Configuration of default website locations and bindings
> > ISA Defaults
> > ISA Custom Rules
> > ISA Client configuration if IP was specified for the configuration
target
> >
> > Shutdown and restart. Check for errors.
> >
> > At each client station, release and renew IP
> > Check for static entries in WINS/DNS
> >
> >
> >
>
>



Re: two machines, same problem, Exchange Drive M by harpert

harpert
Sat Sep 20 10:52:52 CDT 2003

No.... it happens ALL the time and on both machines...
Both on the same type of Internet Connection.

If I disconnect the cable vrom the External adapter during startup.... NO
problem
If the second NIC is connected to Internet during startup...
No drive M, No Exchange
No RPC....
Nothing...

What could possibly be the cause....
Binding order is checked...

1st: Internal
2nd External
3d RAS

Harpert
"Jeff Middleton [SBS-MVP]" <jeff@cfisolutions.com> schreef in bericht
news:uECkSKwfDHA.2152@tk2msftngp13.phx.gbl...
> So is the issue that you can't reboot with the NIC attached to the router
or
> that it happened just the one time and not again?
>
> "harpert" <nomail@mail.com> wrote in message
> news:#LV9S#vfDHA.1752@TK2MSFTNGP10.phx.gbl...
> > Dear Jeff,
> >
> > No (ofcourse) I did NOT change the IPaddress of the internal adapter.
> >
> > I just changed the INTERNET connection from a simple router with
Internal
> > IPaddress 192.168.1.1 connected to the servers external NIC (ip
> > 192.168.1.10)
> > The router was set to DMZ.
> >
> > NOW the server is connected to Internet using ROUTED subnet (Versatel)
> > This means you get a simple router and 8 IPaddresses.
> > Actually you can only use 5 of them.
> > As an example:
> >
> > The IpAddresses are as follows:
> > 11.22.33.120 (used by versatel)
> > 11.22.33.121 (used by the router (gateway))
> > 11.22.33.122
> > 11.22.33.123
> > 11.22.33.124
> > 11.22.33.125
> > 11.22.33.126
> > 11.22.33.127 (used by Versatel)
> >
> > I connected the server (external NIC) to this router using a switch.
> > I set the IPAddress to:
> > 11.22.33.125
> > gateway to:
> > 11.22.33.121
> > DNS to the servers internal IPaddress:
> > 10.0.0.3
> >
> > I ran the ICW.....
> > Told the ICW I want to use 2 nics
> > Point to the IP address of the router: (11.22.33.121)
> > And to the public DNS of Versatel: 62.58.62.132
> >
> > I restarted the SBS and...... everything ran stuck.....
> > NO drive M
> > NO start of exchange
> > No start of RPC...
> >
> > I now disconnected the External Nic from the router.
> > Restarted and waited untill I could connect to the server using TS on a
> > laptop on the Internal NIC using a second switch.
> >
> > NOW there was NO problem....
> > Afterwards I reconnected the external nic to the router...
> > And... everything works FINE....
> >
> > This is a complete riddle to me...............
> >
> > Harpert
> >
> > dleton [SBS-MVP]" <jeff@cfisolutions.com> schreef in bericht
> > news:uXql9lvfDHA.1700@TK2MSFTNGP10.phx.gbl...
> > > Did I follow correctly from your post that you change the IP of the
> > primary
> > > nic on an SBS?
> > >
> > > When you do this, you will need to revise many other things, including
> the
> > > DHCP, DNS, WINS, perhaps RRAS configuration as well. Here's some
> > > information I put together
> > > Changing the IP with SBS 2000
> > >
> > >
> > > There's no problem with changing the IP, though it's enough of a
hassle
> > that
> > > you usually would want to avoid doing it if you can. I'm going to
post
> a
> > > list things to look for, but not detailed instructions. If you have a
> > > problem, post back the specifics of what you need:
> > >
> > > (these are approximately the order I would address it too)
> > >
> > > Primary NIC IP
> > > DNS on the Primary NIC
> > > Any static entries in the WINS/DNS tab on the primary NIC
> > >
> > > DHCP Server Scope
> > > WINS Server database refresh (probably delete the entire contents)
> > > RRAS DHCP Scope if you have entries listed there
> > >
> > > DNS Zones
> > > DNS Reverse Lookups
> > > Flush and restart the DNS entries
> > >
> > > (if any used)
> > > HOSTS
> > > LMHOSTS
> > > Static Routes, if any
> > >
> > > I think these are all fixed with the Internet Connection Wizard, but
> > check:
> > > Exchange
> > > IIS Configuration of default website locations and bindings
> > > ISA Defaults
> > > ISA Custom Rules
> > > ISA Client configuration if IP was specified for the configuration
> target
> > >
> > > Shutdown and restart. Check for errors.
> > >
> > > At each client station, release and renew IP
> > > Check for static entries in WINS/DNS
> > >
> > >
> > >
> >
> >
>
>



Re: two machines, same problem, Exchange Drive M by Jeff

Jeff
Sat Sep 20 11:10:03 CDT 2003

This will kill you.

I've seen this exact condition before. :)

In my case, what happened was that the ISP involved at the customer site
(this was a large commercial building providing a building wide hosting to
the web) was triggering to block this particular IP from being claimed via
DHCP. The IP my server wanted was 10.0.0.2 and for some stupid reason, that
very IP had been claimed in DHCP scope. When my SBS server started up, it
"announced" the intention to use this IP, my guess is by doing a DHCP
request for the IP. Regardless, what was happening is that another device
was indicating that that IP was already in use, and as such, my server said
"oh, nevermind, I won't use that IP then". Well, this doesn't work for an
SBS server. If you abandon the IP, you get no AD, no WINS, no DHCP, etc.

The solution I had while diagnosing this was to unplug, finish the boot,
plug in.

What I found was if the server was off the LAN, on another machine on the
network I could check the ARP cache and the IP was in use. I found the MAC
address that way. From there, I hunted the building with this information
and made the ISP come clean that they have been trying to defeat my server
from using this IP because of heavy traffic....but that wasn't allowed in
the contract.


"harpert" <nomail@mail.com> wrote in message
news:#W5Of94fDHA.1764@TK2MSFTNGP09.phx.gbl...
> No.... it happens ALL the time and on both machines...
> Both on the same type of Internet Connection.
>
> If I disconnect the cable vrom the External adapter during startup.... NO
> problem
> If the second NIC is connected to Internet during startup...
> No drive M, No Exchange
> No RPC....
> Nothing...
>
> What could possibly be the cause....
> Binding order is checked...
>
> 1st: Internal
> 2nd External
> 3d RAS
>
> Harpert
> "Jeff Middleton [SBS-MVP]" <jeff@cfisolutions.com> schreef in bericht
> news:uECkSKwfDHA.2152@tk2msftngp13.phx.gbl...
> > So is the issue that you can't reboot with the NIC attached to the
router
> or
> > that it happened just the one time and not again?
> >
> > "harpert" <nomail@mail.com> wrote in message
> > news:#LV9S#vfDHA.1752@TK2MSFTNGP10.phx.gbl...
> > > Dear Jeff,
> > >
> > > No (ofcourse) I did NOT change the IPaddress of the internal adapter.
> > >
> > > I just changed the INTERNET connection from a simple router with
> Internal
> > > IPaddress 192.168.1.1 connected to the servers external NIC (ip
> > > 192.168.1.10)
> > > The router was set to DMZ.
> > >
> > > NOW the server is connected to Internet using ROUTED subnet (Versatel)
> > > This means you get a simple router and 8 IPaddresses.
> > > Actually you can only use 5 of them.
> > > As an example:
> > >
> > > The IpAddresses are as follows:
> > > 11.22.33.120 (used by versatel)
> > > 11.22.33.121 (used by the router (gateway))
> > > 11.22.33.122
> > > 11.22.33.123
> > > 11.22.33.124
> > > 11.22.33.125
> > > 11.22.33.126
> > > 11.22.33.127 (used by Versatel)
> > >
> > > I connected the server (external NIC) to this router using a switch.
> > > I set the IPAddress to:
> > > 11.22.33.125
> > > gateway to:
> > > 11.22.33.121
> > > DNS to the servers internal IPaddress:
> > > 10.0.0.3
> > >
> > > I ran the ICW.....
> > > Told the ICW I want to use 2 nics
> > > Point to the IP address of the router: (11.22.33.121)
> > > And to the public DNS of Versatel: 62.58.62.132
> > >
> > > I restarted the SBS and...... everything ran stuck.....
> > > NO drive M
> > > NO start of exchange
> > > No start of RPC...
> > >
> > > I now disconnected the External Nic from the router.
> > > Restarted and waited untill I could connect to the server using TS on
a
> > > laptop on the Internal NIC using a second switch.
> > >
> > > NOW there was NO problem....
> > > Afterwards I reconnected the external nic to the router...
> > > And... everything works FINE....
> > >
> > > This is a complete riddle to me...............
> > >
> > > Harpert
> > >
> > > dleton [SBS-MVP]" <jeff@cfisolutions.com> schreef in bericht
> > > news:uXql9lvfDHA.1700@TK2MSFTNGP10.phx.gbl...
> > > > Did I follow correctly from your post that you change the IP of the
> > > primary
> > > > nic on an SBS?
> > > >
> > > > When you do this, you will need to revise many other things,
including
> > the
> > > > DHCP, DNS, WINS, perhaps RRAS configuration as well. Here's some
> > > > information I put together
> > > > Changing the IP with SBS 2000
> > > >
> > > >
> > > > There's no problem with changing the IP, though it's enough of a
> hassle
> > > that
> > > > you usually would want to avoid doing it if you can. I'm going to
> post
> > a
> > > > list things to look for, but not detailed instructions. If you have
a
> > > > problem, post back the specifics of what you need:
> > > >
> > > > (these are approximately the order I would address it too)
> > > >
> > > > Primary NIC IP
> > > > DNS on the Primary NIC
> > > > Any static entries in the WINS/DNS tab on the primary NIC
> > > >
> > > > DHCP Server Scope
> > > > WINS Server database refresh (probably delete the entire contents)
> > > > RRAS DHCP Scope if you have entries listed there
> > > >
> > > > DNS Zones
> > > > DNS Reverse Lookups
> > > > Flush and restart the DNS entries
> > > >
> > > > (if any used)
> > > > HOSTS
> > > > LMHOSTS
> > > > Static Routes, if any
> > > >
> > > > I think these are all fixed with the Internet Connection Wizard, but
> > > check:
> > > > Exchange
> > > > IIS Configuration of default website locations and bindings
> > > > ISA Defaults
> > > > ISA Custom Rules
> > > > ISA Client configuration if IP was specified for the configuration
> > target
> > > >
> > > > Shutdown and restart. Check for errors.
> > > >
> > > > At each client station, release and renew IP
> > > > Check for static entries in WINS/DNS
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>



Re: two machines, same problem, Exchange Drive M by Jeff

Jeff
Sat Sep 20 14:51:35 CDT 2003

Rereading my own post, I anticipate a question you are going to ask.

Yes, the SBS was set to a static IP at 10.0.0.x, but effectively what was
happening was when the SBS booted, it was being told that IP already existed
on the LAN and therefore the SBS didn't use it, therefore everything that
binds to that IP failed on startup.

"Jeff Middleton [SBS-MVP]" <jeff@cfisolutions.com> wrote in message
news:OY5HpE5fDHA.616@TK2MSFTNGP11.phx.gbl...
> This will kill you.
>
> I've seen this exact condition before. :)
>
> In my case, what happened was that the ISP involved at the customer site
> (this was a large commercial building providing a building wide hosting to
> the web) was triggering to block this particular IP from being claimed via
> DHCP. The IP my server wanted was 10.0.0.2 and for some stupid reason,
that
> very IP had been claimed in DHCP scope. When my SBS server started up, it
> "announced" the intention to use this IP, my guess is by doing a DHCP
> request for the IP. Regardless, what was happening is that another device
> was indicating that that IP was already in use, and as such, my server
said
> "oh, nevermind, I won't use that IP then". Well, this doesn't work for an
> SBS server. If you abandon the IP, you get no AD, no WINS, no DHCP, etc.
>
> The solution I had while diagnosing this was to unplug, finish the boot,
> plug in.
>
> What I found was if the server was off the LAN, on another machine on the
> network I could check the ARP cache and the IP was in use. I found the MAC
> address that way. From there, I hunted the building with this information
> and made the ISP come clean that they have been trying to defeat my server
> from using this IP because of heavy traffic....but that wasn't allowed in
> the contract.
>
>
> "harpert" <nomail@mail.com> wrote in message
> news:#W5Of94fDHA.1764@TK2MSFTNGP09.phx.gbl...
> > No.... it happens ALL the time and on both machines...
> > Both on the same type of Internet Connection.
> >
> > If I disconnect the cable vrom the External adapter during startup....
NO
> > problem
> > If the second NIC is connected to Internet during startup...
> > No drive M, No Exchange
> > No RPC....
> > Nothing...
> >
> > What could possibly be the cause....
> > Binding order is checked...
> >
> > 1st: Internal
> > 2nd External
> > 3d RAS
> >
> > Harpert
> > "Jeff Middleton [SBS-MVP]" <jeff@cfisolutions.com> schreef in bericht
> > news:uECkSKwfDHA.2152@tk2msftngp13.phx.gbl...
> > > So is the issue that you can't reboot with the NIC attached to the
> router
> > or
> > > that it happened just the one time and not again?
> > >
> > > "harpert" <nomail@mail.com> wrote in message
> > > news:#LV9S#vfDHA.1752@TK2MSFTNGP10.phx.gbl...
> > > > Dear Jeff,
> > > >
> > > > No (ofcourse) I did NOT change the IPaddress of the internal
adapter.
> > > >
> > > > I just changed the INTERNET connection from a simple router with
> > Internal
> > > > IPaddress 192.168.1.1 connected to the servers external NIC (ip
> > > > 192.168.1.10)
> > > > The router was set to DMZ.
> > > >
> > > > NOW the server is connected to Internet using ROUTED subnet
(Versatel)
> > > > This means you get a simple router and 8 IPaddresses.
> > > > Actually you can only use 5 of them.
> > > > As an example:
> > > >
> > > > The IpAddresses are as follows:
> > > > 11.22.33.120 (used by versatel)
> > > > 11.22.33.121 (used by the router (gateway))
> > > > 11.22.33.122
> > > > 11.22.33.123
> > > > 11.22.33.124
> > > > 11.22.33.125
> > > > 11.22.33.126
> > > > 11.22.33.127 (used by Versatel)
> > > >
> > > > I connected the server (external NIC) to this router using a switch.
> > > > I set the IPAddress to:
> > > > 11.22.33.125
> > > > gateway to:
> > > > 11.22.33.121
> > > > DNS to the servers internal IPaddress:
> > > > 10.0.0.3
> > > >
> > > > I ran the ICW.....
> > > > Told the ICW I want to use 2 nics
> > > > Point to the IP address of the router: (11.22.33.121)
> > > > And to the public DNS of Versatel: 62.58.62.132
> > > >
> > > > I restarted the SBS and...... everything ran stuck.....
> > > > NO drive M
> > > > NO start of exchange
> > > > No start of RPC...
> > > >
> > > > I now disconnected the External Nic from the router.
> > > > Restarted and waited untill I could connect to the server using TS
on
> a
> > > > laptop on the Internal NIC using a second switch.
> > > >
> > > > NOW there was NO problem....
> > > > Afterwards I reconnected the external nic to the router...
> > > > And... everything works FINE....
> > > >
> > > > This is a complete riddle to me...............
> > > >
> > > > Harpert
> > > >
> > > > dleton [SBS-MVP]" <jeff@cfisolutions.com> schreef in bericht
> > > > news:uXql9lvfDHA.1700@TK2MSFTNGP10.phx.gbl...
> > > > > Did I follow correctly from your post that you change the IP of
the
> > > > primary
> > > > > nic on an SBS?
> > > > >
> > > > > When you do this, you will need to revise many other things,
> including
> > > the
> > > > > DHCP, DNS, WINS, perhaps RRAS configuration as well. Here's some
> > > > > information I put together
> > > > > Changing the IP with SBS 2000
> > > > >
> > > > >
> > > > > There's no problem with changing the IP, though it's enough of a
> > hassle
> > > > that
> > > > > you usually would want to avoid doing it if you can. I'm going to
> > post
> > > a
> > > > > list things to look for, but not detailed instructions. If you
have
> a
> > > > > problem, post back the specifics of what you need:
> > > > >
> > > > > (these are approximately the order I would address it too)
> > > > >
> > > > > Primary NIC IP
> > > > > DNS on the Primary NIC
> > > > > Any static entries in the WINS/DNS tab on the primary NIC
> > > > >
> > > > > DHCP Server Scope
> > > > > WINS Server database refresh (probably delete the entire contents)
> > > > > RRAS DHCP Scope if you have entries listed there
> > > > >
> > > > > DNS Zones
> > > > > DNS Reverse Lookups
> > > > > Flush and restart the DNS entries
> > > > >
> > > > > (if any used)
> > > > > HOSTS
> > > > > LMHOSTS
> > > > > Static Routes, if any
> > > > >
> > > > > I think these are all fixed with the Internet Connection Wizard,
but
> > > > check:
> > > > > Exchange
> > > > > IIS Configuration of default website locations and bindings
> > > > > ISA Defaults
> > > > > ISA Custom Rules
> > > > > ISA Client configuration if IP was specified for the configuration
> > > target
> > > > >
> > > > > Shutdown and restart. Check for errors.
> > > > >
> > > > > At each client station, release and renew IP
> > > > > Check for static entries in WINS/DNS
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>



Re: two machines, same problem, Exchange Drive M by Henry

Henry
Sat Sep 20 15:05:06 CDT 2003

Now that -is- an amazing tale of deceit.

Henry Craven
--------------------
Porcupine 3.14159

"Jeff Middleton [SBS-MVP]" <jeff@cfisolutions.com> wrote in message
news:OY5HpE5fDHA.616@TK2MSFTNGP11.phx.gbl...
> This will kill you.
< SNIP>



Re: two machines, same problem, Exchange Drive M by harpert

harpert
Sun Sep 21 13:29:30 CDT 2003

Although this helps me a bit.....
What can I DO about it?????

Thanks Harpert
"Jeff Middleton [SBS-MVP]" <jeff@cfisolutions.com> schreef in bericht
news:%23xOsbA7fDHA.2260@TK2MSFTNGP10.phx.gbl...
> Rereading my own post, I anticipate a question you are going to ask.
>
> Yes, the SBS was set to a static IP at 10.0.0.x, but effectively what was
> happening was when the SBS booted, it was being told that IP already
existed
> on the LAN and therefore the SBS didn't use it, therefore everything that
> binds to that IP failed on startup.
>
> "Jeff Middleton [SBS-MVP]" <jeff@cfisolutions.com> wrote in message
> news:OY5HpE5fDHA.616@TK2MSFTNGP11.phx.gbl...
> > This will kill you.
> >
> > I've seen this exact condition before. :)
> >
> > In my case, what happened was that the ISP involved at the customer site
> > (this was a large commercial building providing a building wide hosting
to
> > the web) was triggering to block this particular IP from being claimed
via
> > DHCP. The IP my server wanted was 10.0.0.2 and for some stupid reason,
> that
> > very IP had been claimed in DHCP scope. When my SBS server started up,
it
> > "announced" the intention to use this IP, my guess is by doing a DHCP
> > request for the IP. Regardless, what was happening is that another
device
> > was indicating that that IP was already in use, and as such, my server
> said
> > "oh, nevermind, I won't use that IP then". Well, this doesn't work for
an
> > SBS server. If you abandon the IP, you get no AD, no WINS, no DHCP, etc.
> >
> > The solution I had while diagnosing this was to unplug, finish the boot,
> > plug in.
> >
> > What I found was if the server was off the LAN, on another machine on
the
> > network I could check the ARP cache and the IP was in use. I found the
MAC
> > address that way. From there, I hunted the building with this
information
> > and made the ISP come clean that they have been trying to defeat my
server
> > from using this IP because of heavy traffic....but that wasn't allowed
in
> > the contract.
> >
> >
> > "harpert" <nomail@mail.com> wrote in message
> > news:#W5Of94fDHA.1764@TK2MSFTNGP09.phx.gbl...
> > > No.... it happens ALL the time and on both machines...
> > > Both on the same type of Internet Connection.
> > >
> > > If I disconnect the cable vrom the External adapter during startup....
> NO
> > > problem
> > > If the second NIC is connected to Internet during startup...
> > > No drive M, No Exchange
> > > No RPC....
> > > Nothing...
> > >
> > > What could possibly be the cause....
> > > Binding order is checked...
> > >
> > > 1st: Internal
> > > 2nd External
> > > 3d RAS
> > >
> > > Harpert
> > > "Jeff Middleton [SBS-MVP]" <jeff@cfisolutions.com> schreef in bericht
> > > news:uECkSKwfDHA.2152@tk2msftngp13.phx.gbl...
> > > > So is the issue that you can't reboot with the NIC attached to the
> > router
> > > or
> > > > that it happened just the one time and not again?
> > > >
> > > > "harpert" <nomail@mail.com> wrote in message
> > > > news:#LV9S#vfDHA.1752@TK2MSFTNGP10.phx.gbl...
> > > > > Dear Jeff,
> > > > >
> > > > > No (ofcourse) I did NOT change the IPaddress of the internal
> adapter.
> > > > >
> > > > > I just changed the INTERNET connection from a simple router with
> > > Internal
> > > > > IPaddress 192.168.1.1 connected to the servers external NIC (ip
> > > > > 192.168.1.10)
> > > > > The router was set to DMZ.
> > > > >
> > > > > NOW the server is connected to Internet using ROUTED subnet
> (Versatel)
> > > > > This means you get a simple router and 8 IPaddresses.
> > > > > Actually you can only use 5 of them.
> > > > > As an example:
> > > > >
> > > > > The IpAddresses are as follows:
> > > > > 11.22.33.120 (used by versatel)
> > > > > 11.22.33.121 (used by the router (gateway))
> > > > > 11.22.33.122
> > > > > 11.22.33.123
> > > > > 11.22.33.124
> > > > > 11.22.33.125
> > > > > 11.22.33.126
> > > > > 11.22.33.127 (used by Versatel)
> > > > >
> > > > > I connected the server (external NIC) to this router using a
switch.
> > > > > I set the IPAddress to:
> > > > > 11.22.33.125
> > > > > gateway to:
> > > > > 11.22.33.121
> > > > > DNS to the servers internal IPaddress:
> > > > > 10.0.0.3
> > > > >
> > > > > I ran the ICW.....
> > > > > Told the ICW I want to use 2 nics
> > > > > Point to the IP address of the router: (11.22.33.121)
> > > > > And to the public DNS of Versatel: 62.58.62.132
> > > > >
> > > > > I restarted the SBS and...... everything ran stuck.....
> > > > > NO drive M
> > > > > NO start of exchange
> > > > > No start of RPC...
> > > > >
> > > > > I now disconnected the External Nic from the router.
> > > > > Restarted and waited untill I could connect to the server using TS
> on
> > a
> > > > > laptop on the Internal NIC using a second switch.
> > > > >
> > > > > NOW there was NO problem....
> > > > > Afterwards I reconnected the external nic to the router...
> > > > > And... everything works FINE....
> > > > >
> > > > > This is a complete riddle to me...............
> > > > >
> > > > > Harpert
> > > > >
> > > > > dleton [SBS-MVP]" <jeff@cfisolutions.com> schreef in bericht
> > > > > news:uXql9lvfDHA.1700@TK2MSFTNGP10.phx.gbl...
> > > > > > Did I follow correctly from your post that you change the IP of
> the
> > > > > primary
> > > > > > nic on an SBS?
> > > > > >
> > > > > > When you do this, you will need to revise many other things,
> > including
> > > > the
> > > > > > DHCP, DNS, WINS, perhaps RRAS configuration as well. Here's
some
> > > > > > information I put together
> > > > > > Changing the IP with SBS 2000
> > > > > >
> > > > > >
> > > > > > There's no problem with changing the IP, though it's enough of a
> > > hassle
> > > > > that
> > > > > > you usually would want to avoid doing it if you can. I'm going
to
> > > post
> > > > a
> > > > > > list things to look for, but not detailed instructions. If you
> have
> > a
> > > > > > problem, post back the specifics of what you need:
> > > > > >
> > > > > > (these are approximately the order I would address it too)
> > > > > >
> > > > > > Primary NIC IP
> > > > > > DNS on the Primary NIC
> > > > > > Any static entries in the WINS/DNS tab on the primary NIC
> > > > > >
> > > > > > DHCP Server Scope
> > > > > > WINS Server database refresh (probably delete the entire
contents)
> > > > > > RRAS DHCP Scope if you have entries listed there
> > > > > >
> > > > > > DNS Zones
> > > > > > DNS Reverse Lookups
> > > > > > Flush and restart the DNS entries
> > > > > >
> > > > > > (if any used)
> > > > > > HOSTS
> > > > > > LMHOSTS
> > > > > > Static Routes, if any
> > > > > >
> > > > > > I think these are all fixed with the Internet Connection Wizard,
> but
> > > > > check:
> > > > > > Exchange
> > > > > > IIS Configuration of default website locations and bindings
> > > > > > ISA Defaults
> > > > > > ISA Custom Rules
> > > > > > ISA Client configuration if IP was specified for the
configuration
> > > > target
> > > > > >
> > > > > > Shutdown and restart. Check for errors.
> > > > > >
> > > > > > At each client station, release and renew IP
> > > > > > Check for static entries in WINS/DNS
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>



Re: two machines, same problem, Exchange Drive M by Marina

Marina
Sun Sep 21 13:39:15 CDT 2003

Check everything again. All TCP/IP properties of all nics, bindingorder,
DHCP, DNS, WINS (if you have W9x, ME or NT4 clients).
Run ICW again.
Reboot.
Which errormessages do you get?

Marina

"harpert" <nomail@mail.com> schreef in bericht
news:%2311Zs5GgDHA.128@tk2msftngp13.phx.gbl...
> Although this helps me a bit.....
> What can I DO about it?????
>
> Thanks Harpert
> "Jeff Middleton [SBS-MVP]" <jeff@cfisolutions.com> schreef in bericht
> news:%23xOsbA7fDHA.2260@TK2MSFTNGP10.phx.gbl...
> > Rereading my own post, I anticipate a question you are going to ask.
> >
> > Yes, the SBS was set to a static IP at 10.0.0.x, but effectively what
was
> > happening was when the SBS booted, it was being told that IP already
> existed
> > on the LAN and therefore the SBS didn't use it, therefore everything
that
> > binds to that IP failed on startup.
> >
> > "Jeff Middleton [SBS-MVP]" <jeff@cfisolutions.com> wrote in message
> > news:OY5HpE5fDHA.616@TK2MSFTNGP11.phx.gbl...
> > > This will kill you.
> > >
> > > I've seen this exact condition before. :)
> > >
> > > In my case, what happened was that the ISP involved at the customer
site
> > > (this was a large commercial building providing a building wide
hosting
> to
> > > the web) was triggering to block this particular IP from being claimed
> via
> > > DHCP. The IP my server wanted was 10.0.0.2 and for some stupid
reason,
> > that
> > > very IP had been claimed in DHCP scope. When my SBS server started up,
> it
> > > "announced" the intention to use this IP, my guess is by doing a DHCP
> > > request for the IP. Regardless, what was happening is that another
> device
> > > was indicating that that IP was already in use, and as such, my server
> > said
> > > "oh, nevermind, I won't use that IP then". Well, this doesn't work for
> an
> > > SBS server. If you abandon the IP, you get no AD, no WINS, no DHCP,
etc.
> > >
> > > The solution I had while diagnosing this was to unplug, finish the
boot,
> > > plug in.
> > >
> > > What I found was if the server was off the LAN, on another machine on
> the
> > > network I could check the ARP cache and the IP was in use. I found the
> MAC
> > > address that way. From there, I hunted the building with this
> information
> > > and made the ISP come clean that they have been trying to defeat my
> server
> > > from using this IP because of heavy traffic....but that wasn't allowed
> in
> > > the contract.
> > >
> > >
> > > "harpert" <nomail@mail.com> wrote in message
> > > news:#W5Of94fDHA.1764@TK2MSFTNGP09.phx.gbl...
> > > > No.... it happens ALL the time and on both machines...
> > > > Both on the same type of Internet Connection.
> > > >
> > > > If I disconnect the cable vrom the External adapter during
startup....
> > NO
> > > > problem
> > > > If the second NIC is connected to Internet during startup...
> > > > No drive M, No Exchange
> > > > No RPC....
> > > > Nothing...
> > > >
> > > > What could possibly be the cause....
> > > > Binding order is checked...
> > > >
> > > > 1st: Internal
> > > > 2nd External
> > > > 3d RAS
> > > >
> > > > Harpert
> > > > "Jeff Middleton [SBS-MVP]" <jeff@cfisolutions.com> schreef in
bericht
> > > > news:uECkSKwfDHA.2152@tk2msftngp13.phx.gbl...
> > > > > So is the issue that you can't reboot with the NIC attached to the
> > > router
> > > > or
> > > > > that it happened just the one time and not again?
> > > > >
> > > > > "harpert" <nomail@mail.com> wrote in message
> > > > > news:#LV9S#vfDHA.1752@TK2MSFTNGP10.phx.gbl...
> > > > > > Dear Jeff,
> > > > > >
> > > > > > No (ofcourse) I did NOT change the IPaddress of the internal
> > adapter.
> > > > > >
> > > > > > I just changed the INTERNET connection from a simple router with
> > > > Internal
> > > > > > IPaddress 192.168.1.1 connected to the servers external NIC (ip
> > > > > > 192.168.1.10)
> > > > > > The router was set to DMZ.
> > > > > >
> > > > > > NOW the server is connected to Internet using ROUTED subnet
> > (Versatel)
> > > > > > This means you get a simple router and 8 IPaddresses.
> > > > > > Actually you can only use 5 of them.
> > > > > > As an example:
> > > > > >
> > > > > > The IpAddresses are as follows:
> > > > > > 11.22.33.120 (used by versatel)
> > > > > > 11.22.33.121 (used by the router (gateway))
> > > > > > 11.22.33.122
> > > > > > 11.22.33.123
> > > > > > 11.22.33.124
> > > > > > 11.22.33.125
> > > > > > 11.22.33.126
> > > > > > 11.22.33.127 (used by Versatel)
> > > > > >
> > > > > > I connected the server (external NIC) to this router using a
> switch.
> > > > > > I set the IPAddress to:
> > > > > > 11.22.33.125
> > > > > > gateway to:
> > > > > > 11.22.33.121
> > > > > > DNS to the servers internal IPaddress:
> > > > > > 10.0.0.3
> > > > > >
> > > > > > I ran the ICW.....
> > > > > > Told the ICW I want to use 2 nics
> > > > > > Point to the IP address of the router: (11.22.33.121)
> > > > > > And to the public DNS of Versatel: 62.58.62.132
> > > > > >
> > > > > > I restarted the SBS and...... everything ran stuck.....
> > > > > > NO drive M
> > > > > > NO start of exchange
> > > > > > No start of RPC...
> > > > > >
> > > > > > I now disconnected the External Nic from the router.
> > > > > > Restarted and waited untill I could connect to the server using
TS
> > on
> > > a
> > > > > > laptop on the Internal NIC using a second switch.
> > > > > >
> > > > > > NOW there was NO problem....
> > > > > > Afterwards I reconnected the external nic to the router...
> > > > > > And... everything works FINE....
> > > > > >
> > > > > > This is a complete riddle to me...............
> > > > > >
> > > > > > Harpert
> > > > > >
> > > > > > dleton [SBS-MVP]" <jeff@cfisolutions.com> schreef in bericht
> > > > > > news:uXql9lvfDHA.1700@TK2MSFTNGP10.phx.gbl...
> > > > > > > Did I follow correctly from your post that you change the IP
of
> > the
> > > > > > primary
> > > > > > > nic on an SBS?
> > > > > > >
> > > > > > > When you do this, you will need to revise many other things,
> > > including
> > > > > the
> > > > > > > DHCP, DNS, WINS, perhaps RRAS configuration as well. Here's
> some
> > > > > > > information I put together
> > > > > > > Changing the IP with SBS 2000
> > > > > > >
> > > > > > >
> > > > > > > There's no problem with changing the IP, though it's enough of
a
> > > > hassle
> > > > > > that
> > > > > > > you usually would want to avoid doing it if you can. I'm
going
> to
> > > > post
> > > > > a
> > > > > > > list things to look for, but not detailed instructions. If you
> > have
> > > a
> > > > > > > problem, post back the specifics of what you need:
> > > > > > >
> > > > > > > (these are approximately the order I would address it too)
> > > > > > >
> > > > > > > Primary NIC IP
> > > > > > > DNS on the Primary NIC
> > > > > > > Any static entries in the WINS/DNS tab on the primary NIC
> > > > > > >
> > > > > > > DHCP Server Scope
> > > > > > > WINS Server database refresh (probably delete the entire
> contents)
> > > > > > > RRAS DHCP Scope if you have entries listed there
> > > > > > >
> > > > > > > DNS Zones
> > > > > > > DNS Reverse Lookups
> > > > > > > Flush and restart the DNS entries
> > > > > > >
> > > > > > > (if any used)
> > > > > > > HOSTS
> > > > > > > LMHOSTS
> > > > > > > Static Routes, if any
> > > > > > >
> > > > > > > I think these are all fixed with the Internet Connection
Wizard,
> > but
> > > > > > check:
> > > > > > > Exchange
> > > > > > > IIS Configuration of default website locations and bindings
> > > > > > > ISA Defaults
> > > > > > > ISA Custom Rules
> > > > > > > ISA Client configuration if IP was specified for the
> configuration
> > > > > target
> > > > > > >
> > > > > > > Shutdown and restart. Check for errors.
> > > > > > >
> > > > > > > At each client station, release and renew IP
> > > > > > > Check for static entries in WINS/DNS
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>



Re: two machines, same problem, Exchange Drive M by Jeff

Jeff
Sun Sep 21 13:44:54 CDT 2003

The implication is that you need to repeat my discovery. Connect another
computer on the wire and subnet that causes the boot to fail. Now, boot the
Server and then, using the ARP cache you can pull on the second computer,
determine if there's another device on the subnet that is attempting to
block that IP from being used. In my case, it was a subnet that was part of
an entire building....way to much to do a trial an error test. In your
case, I suspect that if you simply disconnect or substitute the
switch/router or just power them off instead of unplugging the SBS cable,
you will be able to determine which device is causing your problem. From
there, dig into why your SBS is being denied an IP.

In addition, when I inspected the Event Log, I saw an error indicating that
the IP was already in use during the boot sequence.

To repair this problem, you will need to know what the cause is, but
identifying the device causing it is the first step.


"harpert" <nomail@mail.com> wrote in message
news:#11Zs5GgDHA.128@tk2msftngp13.phx.gbl...
> Although this helps me a bit.....
> What can I DO about it?????
>
> Thanks Harpert
> "Jeff Middleton [SBS-MVP]" <jeff@cfisolutions.com> schreef in bericht
> news:%23xOsbA7fDHA.2260@TK2MSFTNGP10.phx.gbl...
> > Rereading my own post, I anticipate a question you are going to ask.
> >
> > Yes, the SBS was set to a static IP at 10.0.0.x, but effectively what
was
> > happening was when the SBS booted, it was being told that IP already
> existed
> > on the LAN and therefore the SBS didn't use it, therefore everything
that
> > binds to that IP failed on startup.
> >
> > "Jeff Middleton [SBS-MVP]" <jeff@cfisolutions.com> wrote in message
> > news:OY5HpE5fDHA.616@TK2MSFTNGP11.phx.gbl...
> > > This will kill you.
> > >
> > > I've seen this exact condition before. :)
> > >
> > > In my case, what happened was that the ISP involved at the customer
site
> > > (this was a large commercial building providing a building wide
hosting
> to
> > > the web) was triggering to block this particular IP from being claimed
> via
> > > DHCP. The IP my server wanted was 10.0.0.2 and for some stupid
reason,
> > that
> > > very IP had been claimed in DHCP scope. When my SBS server started up,
> it
> > > "announced" the intention to use this IP, my guess is by doing a DHCP
> > > request for the IP. Regardless, what was happening is that another
> device
> > > was indicating that that IP was already in use, and as such, my server
> > said
> > > "oh, nevermind, I won't use that IP then". Well, this doesn't work for
> an
> > > SBS server. If you abandon the IP, you get no AD, no WINS, no DHCP,
etc.
> > >
> > > The solution I had while diagnosing this was to unplug, finish the
boot,
> > > plug in.
> > >
> > > What I found was if the server was off the LAN, on another machine on
> the
> > > network I could check the ARP cache and the IP was in use. I found the
> MAC
> > > address that way. From there, I hunted the building with this
> information
> > > and made the ISP come clean that they have been trying to defeat my
> server
> > > from using this IP because of heavy traffic....but that wasn't allowed
> in
> > > the contract.
> > >
> > >
> > > "harpert" <nomail@mail.com> wrote in message
> > > news:#W5Of94fDHA.1764@TK2MSFTNGP09.phx.gbl...
> > > > No.... it happens ALL the time and on both machines...
> > > > Both on the same type of Internet Connection.
> > > >
> > > > If I disconnect the cable vrom the External adapter during
startup....
> > NO
> > > > problem
> > > > If the second NIC is connected to Internet during startup...
> > > > No drive M, No Exchange
> > > > No RPC....
> > > > Nothing...
> > > >
> > > > What could possibly be the cause....
> > > > Binding order is checked...
> > > >
> > > > 1st: Internal
> > > > 2nd External
> > > > 3d RAS
> > > >
> > > > Harpert
> > > > "Jeff Middleton [SBS-MVP]" <jeff@cfisolutions.com> schreef in
bericht
> > > > news:uECkSKwfDHA.2152@tk2msftngp13.phx.gbl...
> > > > > So is the issue that you can't reboot with the NIC attached to the
> > > router
> > > > or
> > > > > that it happened just the one time and not again?
> > > > >
> > > > > "harpert" <nomail@mail.com> wrote in message
> > > > > news:#LV9S#vfDHA.1752@TK2MSFTNGP10.phx.gbl...
> > > > > > Dear Jeff,
> > > > > >
> > > > > > No (ofcourse) I did NOT change the IPaddress of the internal
> > adapter.
> > > > > >
> > > > > > I just changed the INTERNET connection from a simple router with
> > > > Internal
> > > > > > IPaddress 192.168.1.1 connected to the servers external NIC (ip
> > > > > > 192.168.1.10)
> > > > > > The router was set to DMZ.
> > > > > >
> > > > > > NOW the server is connected to Internet using ROUTED subnet
> > (Versatel)
> > > > > > This means you get a simple router and 8 IPaddresses.
> > > > > > Actually you can only use 5 of them.
> > > > > > As an example:
> > > > > >
> > > > > > The IpAddresses are as follows:
> > > > > > 11.22.33.120 (used by versatel)
> > > > > > 11.22.33.121 (used by the router (gateway))
> > > > > > 11.22.33.122
> > > > > > 11.22.33.123
> > > > > > 11.22.33.124
> > > > > > 11.22.33.125
> > > > > > 11.22.33.126
> > > > > > 11.22.33.127 (used by Versatel)
> > > > > >
> > > > > > I connected the server (external NIC) to this router using a
> switch.
> > > > > > I set the IPAddress to:
> > > > > > 11.22.33.125
> > > > > > gateway to:
> > > > > > 11.22.33.121
> > > > > > DNS to the servers internal IPaddress:
> > > > > > 10.0.0.3
> > > > > >
> > > > > > I ran the ICW.....
> > > > > > Told the ICW I want to use 2 nics
> > > > > > Point to the IP address of the router: (11.22.33.121)
> > > > > > And to the public DNS of Versatel: 62.58.62.132
> > > > > >
> > > > > > I restarted the SBS and...... everything ran stuck.....
> > > > > > NO drive M
> > > > > > NO start of exchange
> > > > > > No start of RPC...
> > > > > >
> > > > > > I now disconnected the External Nic from the router.
> > > > > > Restarted and waited untill I could connect to the server using
TS
> > on
> > > a
> > > > > > laptop on the Internal NIC using a second switch.
> > > > > >
> > > > > > NOW there was NO problem....
> > > > > > Afterwards I reconnected the external nic to the router...
> > > > > > And... everything works FINE....
> > > > > >
> > > > > > This is a complete riddle to me...............
> > > > > >
> > > > > > Harpert
> > > > > >
> > > > > > dleton [SBS-MVP]" <jeff@cfisolutions.com> schreef in bericht
> > > > > > news:uXql9lvfDHA.1700@TK2MSFTNGP10.phx.gbl...
> > > > > > > Did I follow correctly from your post that you change the IP
of
> > the
> > > > > > primary
> > > > > > > nic on an SBS?
> > > > > > >
> > > > > > > When you do this, you will need to revise many other things,
> > > including
> > > > > the
> > > > > > > DHCP, DNS, WINS, perhaps RRAS configuration as well. Here's
> some
> > > > > > > information I put together
> > > > > > > Changing the IP with SBS 2000
> > > > > > >
> > > > > > >
> > > > > > > There's no problem with changing the IP, though it's enough of
a
> > > > hassle
> > > > > > that
> > > > > > > you usually would want to avoid doing it if you can. I'm
going
> to
> > > > post
> > > > > a
> > > > > > > list things to look for, but not detailed instructions. If you
> > have
> > > a
> > > > > > > problem, post back the specifics of what you need:
> > > > > > >
> > > > > > > (these are approximately the order I would address it too)
> > > > > > >
> > > > > > > Primary NIC IP
> > > > > > > DNS on the Primary NIC
> > > > > > > Any static entries in the WINS/DNS tab on the primary NIC
> > > > > > >
> > > > > > > DHCP Server Scope
> > > > > > > WINS Server database refresh (probably delete the entire
> contents)
> > > > > > > RRAS DHCP Scope if you have entries listed there
> > > > > > >
> > > > > > > DNS Zones
> > > > > > > DNS Reverse Lookups
> > > > > > > Flush and restart the DNS entries
> > > > > > >
> > > > > > > (if any used)
> > > > > > > HOSTS
> > > > > > > LMHOSTS
> > > > > > > Static Routes, if any
> > > > > > >
> > > > > > > I think these are all fixed with the Internet Connection
Wizard,
> > but
> > > > > > check:
> > > > > > > Exchange
> > > > > > > IIS Configuration of default website locations and bindings
> > > > > > > ISA Defaults
> > > > > > > ISA Custom Rules
> > > > > > > ISA Client configuration if IP was specified for the
> configuration
> > > > > target
> > > > > > >
> > > > > > > Shutdown and restart. Check for errors.
> > > > > > >
> > > > > > > At each client station, release and renew IP
> > > > > > > Check for static entries in WINS/DNS
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>