Configuring SBS 2000 for NAT.

I have a client who is presently using SBS 2000, and is having constant
problems with network connections. Here's what is happening. First, from
time to time he loses connections and has to restart all of his workstations,
and even the server to get he connections back.

(History)
Now, it was setup by somebody else over 5 years ago. Recently, I rebulit him
a new server and loaded back his operating system into it, to get him
running. Except, his network is static IP's with internet through the same
LAN adapter.

What I like to do for him, to solve his problem, is to attach his second LAN
adapter with a router, for the internet, either DHCP or static using NAT.
Then, using a HUB attach all of his computers to the second LAN adater and
configure it to log in each workstation statically. This way, he will not
have these issues again!

Is this a better choice, or is there something else as to why he is having
all of these problems.

What he has, is a DSL modem attached to a wired router, along with all his
clients, and they are seeing the server and logging in and seeing the
internet too.

Please advise if NAT is a good suggestion, I believe he is logging into a
Domain controller... not sure, but can find out.

I appreciate any feedback on this topic!

SuperGumby
Tue Mar 04 16:39:55 CST 2008

I'd probably try to get the current setup reliably working before
implementing any change.

1) Post the current output from 'IPConfig /all' for both the server and one
workstation.
2) If the router has any DHCP ability (they normally do), disable it. Enable
DHCP on the SBS. Set all workstations to get IP's via DHCP from SBS.

Sounds like we can forget everything that happened 5 years ago because you
have re-installed the server. When this was done, did you 'restore' AD from
the old box? migrate it? or simply throw away the old and fresh install? If
it's a fresh installation have the client machines been properly introduced
to the new domain?

"tlc_13200@hotmail.com" <tlc13200hotmailcom@discussions.microsoft.com> wrote
in message news:D35E15A3-EF04-48B6-9693-925A8EE12F84@microsoft.com...
>I have a client who is presently using SBS 2000, and is having constant
> problems with network connections. Here's what is happening. First, from
> time to time he loses connections and has to restart all of his
> workstations,
> and even the server to get he connections back.
>
> (History)
> Now, it was setup by somebody else over 5 years ago. Recently, I rebulit
> him
> a new server and loaded back his operating system into it, to get him
> running. Except, his network is static IP's with internet through the same
> LAN adapter.
>
> What I like to do for him, to solve his problem, is to attach his second
> LAN
> adapter with a router, for the internet, either DHCP or static using NAT.
> Then, using a HUB attach all of his computers to the second LAN adater and
> configure it to log in each workstation statically. This way, he will not
> have these issues again!
>
> Is this a better choice, or is there something else as to why he is having
> all of these problems.
>
> What he has, is a DSL modem attached to a wired router, along with all his
> clients, and they are seeing the server and logging in and seeing the
> internet too.
>
> Please advise if NAT is a good suggestion, I believe he is logging into a
> Domain controller... not sure, but can find out.
>
> I appreciate any feedback on this topic!

tlc13200hotmailcom
Tue Mar 04 16:52:01 CST 2008

Hi SuperGumby,

Thank you for jogging my memory. Actually, no miragation was performed. All
that was done, was a installation and I believe there is an AD. I have to
look at it of course.

But, what I do know, everything is setup statically. No DHCP!

I believe the scheme of IP addresses its behind is 192.168.16.xxx.

However, the DSL modem is plugged into the LINKSys router, and they are
sharing the internet through it. When you say: "Enable DHCP on the SBS. Set
all workstations to get IP's via DHCP from SBS", I was wondering... would it
be best to attach the workstations unto a wired HUB and attach it to the
server, being that their router is failing at times, and program the
workstations that way?

And configuring the workstations to log in dynamically might confused their
printers they have. Which I believe is static. Although, they are HP laser
printer, and inkjet.

I feel that their network connections is failing at times, where they lose
the communication between the workstation and server application. Which is
DENTRIX. A medical software application.

Would enabling SBS to DHCP really solve their problem?


"SuperGumby [SBS MVP]" wrote:

> I'd probably try to get the current setup reliably working before
> implementing any change.
>
> 1) Post the current output from 'IPConfig /all' for both the server and one
> workstation.
> 2) If the router has any DHCP ability (they normally do), disable it. Enable
> DHCP on the SBS. Set all workstations to get IP's via DHCP from SBS.
>
> Sounds like we can forget everything that happened 5 years ago because you
> have re-installed the server. When this was done, did you 'restore' AD from
> the old box? migrate it? or simply throw away the old and fresh install? If
> it's a fresh installation have the client machines been properly introduced
> to the new domain?
>
> "tlc_13200@hotmail.com" <tlc13200hotmailcom@discussions.microsoft.com> wrote
> in message news:D35E15A3-EF04-48B6-9693-925A8EE12F84@microsoft.com...
> >I have a client who is presently using SBS 2000, and is having constant
> > problems with network connections. Here's what is happening. First, from
> > time to time he loses connections and has to restart all of his
> > workstations,
> > and even the server to get he connections back.
> >
> > (History)
> > Now, it was setup by somebody else over 5 years ago. Recently, I rebulit
> > him
> > a new server and loaded back his operating system into it, to get him
> > running. Except, his network is static IP's with internet through the same
> > LAN adapter.
> >
> > What I like to do for him, to solve his problem, is to attach his second
> > LAN
> > adapter with a router, for the internet, either DHCP or static using NAT.
> > Then, using a HUB attach all of his computers to the second LAN adater and
> > configure it to log in each workstation statically. This way, he will not
> > have these issues again!
> >
> > Is this a better choice, or is there something else as to why he is having
> > all of these problems.
> >
> > What he has, is a DSL modem attached to a wired router, along with all his
> > clients, and they are seeing the server and logging in and seeing the
> > internet too.
> >
> > Please advise if NAT is a good suggestion, I believe he is logging into a
> > Domain controller... not sure, but can find out.
> >
> > I appreciate any feedback on this topic!
>
>
>

SuperGumby
Tue Mar 04 16:59:51 CST 2008

Without the current IPConfig from the server and a workstation it is hard to
pass comment. However, _most_ network related problems occur because things
do not happen in the manner SBS requires. The simplest way of fixing this is
to allow SBS to be boss.

The users are not going to be confused by a change from static to dynamic IP
addressing, they don't even see this process. (NOTE: I was wondering what
you meant by 'static logon'.)

"tlc_13200@hotmail.com" <tlc13200hotmailcom@discussions.microsoft.com> wrote
in message news:1E38080C-9978-4241-8114-F8A530252A3C@microsoft.com...
> Hi SuperGumby,
>
> Thank you for jogging my memory. Actually, no miragation was performed.
> All
> that was done, was a installation and I believe there is an AD. I have to
> look at it of course.
>
> But, what I do know, everything is setup statically. No DHCP!
>
> I believe the scheme of IP addresses its behind is 192.168.16.xxx.
>
> However, the DSL modem is plugged into the LINKSys router, and they are
> sharing the internet through it. When you say: "Enable DHCP on the SBS.
> Set
> all workstations to get IP's via DHCP from SBS", I was wondering... would
> it
> be best to attach the workstations unto a wired HUB and attach it to the
> server, being that their router is failing at times, and program the
> workstations that way?
>
> And configuring the workstations to log in dynamically might confused
> their
> printers they have. Which I believe is static. Although, they are HP laser
> printer, and inkjet.
>
> I feel that their network connections is failing at times, where they lose
> the communication between the workstation and server application. Which is
> DENTRIX. A medical software application.
>
> Would enabling SBS to DHCP really solve their problem?
>
>
> "SuperGumby [SBS MVP]" wrote:
>
>> I'd probably try to get the current setup reliably working before
>> implementing any change.
>>
>> 1) Post the current output from 'IPConfig /all' for both the server and
>> one
>> workstation.
>> 2) If the router has any DHCP ability (they normally do), disable it.
>> Enable
>> DHCP on the SBS. Set all workstations to get IP's via DHCP from SBS.
>>
>> Sounds like we can forget everything that happened 5 years ago because
>> you
>> have re-installed the server. When this was done, did you 'restore' AD
>> from
>> the old box? migrate it? or simply throw away the old and fresh install?
>> If
>> it's a fresh installation have the client machines been properly
>> introduced
>> to the new domain?
>>
>> "tlc_13200@hotmail.com" <tlc13200hotmailcom@discussions.microsoft.com>
>> wrote
>> in message news:D35E15A3-EF04-48B6-9693-925A8EE12F84@microsoft.com...
>> >I have a client who is presently using SBS 2000, and is having constant
>> > problems with network connections. Here's what is happening. First,
>> > from
>> > time to time he loses connections and has to restart all of his
>> > workstations,
>> > and even the server to get he connections back.
>> >
>> > (History)
>> > Now, it was setup by somebody else over 5 years ago. Recently, I
>> > rebulit
>> > him
>> > a new server and loaded back his operating system into it, to get him
>> > running. Except, his network is static IP's with internet through the
>> > same
>> > LAN adapter.
>> >
>> > What I like to do for him, to solve his problem, is to attach his
>> > second
>> > LAN
>> > adapter with a router, for the internet, either DHCP or static using
>> > NAT.
>> > Then, using a HUB attach all of his computers to the second LAN adater
>> > and
>> > configure it to log in each workstation statically. This way, he will
>> > not
>> > have these issues again!
>> >
>> > Is this a better choice, or is there something else as to why he is
>> > having
>> > all of these problems.
>> >
>> > What he has, is a DSL modem attached to a wired router, along with all
>> > his
>> > clients, and they are seeing the server and logging in and seeing the
>> > internet too.
>> >
>> > Please advise if NAT is a good suggestion, I believe he is logging into
>> > a
>> > Domain controller... not sure, but can find out.
>> >
>> > I appreciate any feedback on this topic!
>>
>>
>>

tlc13200hotmailcom
Tue Mar 04 17:52:01 CST 2008

Sorry, I should have been more clear. They all have been logging on with a
static IP, instead of dynamic. (Fixed IP instead of DHCP). I know very little
about SBS 2000, compared to 2003, etc. I remembered that NAT had be set in
order for Windows Server 2000 to route the "name address translation" for
both the internet and the workstations to exist together.

But, you are telling me that I have to tell SBS 2000 to confire itself as
DHCP and the problems will go away?!

They are still freezing up with connection issues, and have to constantly
reboot their workstations, and even the server in order for the software to
work again, temporarily of course.

I figured, if I get them a new router and HUB switch, and plug the router
into one LAN adapter, and the HUB into another, and tell SBS 2000 to work
it's NAT that it would operate without the system crashing.

Tell me is it the server causing the problem by not being DHCP?

"SuperGumby [SBS MVP]" wrote:

> Without the current IPConfig from the server and a workstation it is hard to
> pass comment. However, _most_ network related problems occur because things
> do not happen in the manner SBS requires. The simplest way of fixing this is
> to allow SBS to be boss.
>
> The users are not going to be confused by a change from static to dynamic IP
> addressing, they don't even see this process. (NOTE: I was wondering what
> you meant by 'static logon'.)
>
> "tlc_13200@hotmail.com" <tlc13200hotmailcom@discussions.microsoft.com> wrote
> in message news:1E38080C-9978-4241-8114-F8A530252A3C@microsoft.com...
> > Hi SuperGumby,
> >
> > Thank you for jogging my memory. Actually, no miragation was performed.
> > All
> > that was done, was a installation and I believe there is an AD. I have to
> > look at it of course.
> >
> > But, what I do know, everything is setup statically. No DHCP!
> >
> > I believe the scheme of IP addresses its behind is 192.168.16.xxx.
> >
> > However, the DSL modem is plugged into the LINKSys router, and they are
> > sharing the internet through it. When you say: "Enable DHCP on the SBS.
> > Set
> > all workstations to get IP's via DHCP from SBS", I was wondering... would
> > it
> > be best to attach the workstations unto a wired HUB and attach it to the
> > server, being that their router is failing at times, and program the
> > workstations that way?
> >
> > And configuring the workstations to log in dynamically might confused
> > their
> > printers they have. Which I believe is static. Although, they are HP laser
> > printer, and inkjet.
> >
> > I feel that their network connections is failing at times, where they lose
> > the communication between the workstation and server application. Which is
> > DENTRIX. A medical software application.
> >
> > Would enabling SBS to DHCP really solve their problem?
> >
> >
> > "SuperGumby [SBS MVP]" wrote:
> >
> >> I'd probably try to get the current setup reliably working before
> >> implementing any change.
> >>
> >> 1) Post the current output from 'IPConfig /all' for both the server and
> >> one
> >> workstation.
> >> 2) If the router has any DHCP ability (they normally do), disable it.
> >> Enable
> >> DHCP on the SBS. Set all workstations to get IP's via DHCP from SBS.
> >>
> >> Sounds like we can forget everything that happened 5 years ago because
> >> you
> >> have re-installed the server. When this was done, did you 'restore' AD
> >> from
> >> the old box? migrate it? or simply throw away the old and fresh install?
> >> If
> >> it's a fresh installation have the client machines been properly
> >> introduced
> >> to the new domain?
> >>
> >> "tlc_13200@hotmail.com" <tlc13200hotmailcom@discussions.microsoft.com>
> >> wrote
> >> in message news:D35E15A3-EF04-48B6-9693-925A8EE12F84@microsoft.com...
> >> >I have a client who is presently using SBS 2000, and is having constant
> >> > problems with network connections. Here's what is happening. First,
> >> > from
> >> > time to time he loses connections and has to restart all of his
> >> > workstations,
> >> > and even the server to get he connections back.
> >> >
> >> > (History)
> >> > Now, it was setup by somebody else over 5 years ago. Recently, I
> >> > rebulit
> >> > him
> >> > a new server and loaded back his operating system into it, to get him
> >> > running. Except, his network is static IP's with internet through the
> >> > same
> >> > LAN adapter.
> >> >
> >> > What I like to do for him, to solve his problem, is to attach his
> >> > second
> >> > LAN
> >> > adapter with a router, for the internet, either DHCP or static using
> >> > NAT.
> >> > Then, using a HUB attach all of his computers to the second LAN adater
> >> > and
> >> > configure it to log in each workstation statically. This way, he will
> >> > not
> >> > have these issues again!
> >> >
> >> > Is this a better choice, or is there something else as to why he is
> >> > having
> >> > all of these problems.
> >> >
> >> > What he has, is a DSL modem attached to a wired router, along with all
> >> > his
> >> > clients, and they are seeing the server and logging in and seeing the
> >> > internet too.
> >> >
> >> > Please advise if NAT is a good suggestion, I believe he is logging into
> >> > a
> >> > Domain controller... not sure, but can find out.
> >> >
> >> > I appreciate any feedback on this topic!
> >>
> >>
> >>
>
>
>

SuperGumby
Tue Mar 04 18:05:02 CST 2008

The problem is not specifically due to whether or not SBS is doing DHCP. It
is all about the proper configuration of networking.

It is possible to manually configure properly. It is easier to let SBS do it
for you.

Throwing devices at the mix willy-nilly won't fix anything.

"tlc_13200@hotmail.com" <tlc13200hotmailcom@discussions.microsoft.com> wrote
in message news:F133BB91-7974-479E-9F64-63C966C00D5D@microsoft.com...
> Sorry, I should have been more clear. They all have been logging on with a
> static IP, instead of dynamic. (Fixed IP instead of DHCP). I know very
> little
> about SBS 2000, compared to 2003, etc. I remembered that NAT had be set in
> order for Windows Server 2000 to route the "name address translation" for
> both the internet and the workstations to exist together.
>
> But, you are telling me that I have to tell SBS 2000 to confire itself as
> DHCP and the problems will go away?!
>
> They are still freezing up with connection issues, and have to constantly
> reboot their workstations, and even the server in order for the software
> to
> work again, temporarily of course.
>
> I figured, if I get them a new router and HUB switch, and plug the router
> into one LAN adapter, and the HUB into another, and tell SBS 2000 to work
> it's NAT that it would operate without the system crashing.
>
> Tell me is it the server causing the problem by not being DHCP?
>
> "SuperGumby [SBS MVP]" wrote:
>
>> Without the current IPConfig from the server and a workstation it is hard
>> to
>> pass comment. However, _most_ network related problems occur because
>> things
>> do not happen in the manner SBS requires. The simplest way of fixing this
>> is
>> to allow SBS to be boss.
>>
>> The users are not going to be confused by a change from static to dynamic
>> IP
>> addressing, they don't even see this process. (NOTE: I was wondering what
>> you meant by 'static logon'.)
>>
>> "tlc_13200@hotmail.com" <tlc13200hotmailcom@discussions.microsoft.com>
>> wrote
>> in message news:1E38080C-9978-4241-8114-F8A530252A3C@microsoft.com...
>> > Hi SuperGumby,
>> >
>> > Thank you for jogging my memory. Actually, no miragation was performed.
>> > All
>> > that was done, was a installation and I believe there is an AD. I have
>> > to
>> > look at it of course.
>> >
>> > But, what I do know, everything is setup statically. No DHCP!
>> >
>> > I believe the scheme of IP addresses its behind is 192.168.16.xxx.
>> >
>> > However, the DSL modem is plugged into the LINKSys router, and they are
>> > sharing the internet through it. When you say: "Enable DHCP on the SBS.
>> > Set
>> > all workstations to get IP's via DHCP from SBS", I was wondering...
>> > would
>> > it
>> > be best to attach the workstations unto a wired HUB and attach it to
>> > the
>> > server, being that their router is failing at times, and program the
>> > workstations that way?
>> >
>> > And configuring the workstations to log in dynamically might confused
>> > their
>> > printers they have. Which I believe is static. Although, they are HP
>> > laser
>> > printer, and inkjet.
>> >
>> > I feel that their network connections is failing at times, where they
>> > lose
>> > the communication between the workstation and server application. Which
>> > is
>> > DENTRIX. A medical software application.
>> >
>> > Would enabling SBS to DHCP really solve their problem?
>> >
>> >
>> > "SuperGumby [SBS MVP]" wrote:
>> >
>> >> I'd probably try to get the current setup reliably working before
>> >> implementing any change.
>> >>
>> >> 1) Post the current output from 'IPConfig /all' for both the server
>> >> and
>> >> one
>> >> workstation.
>> >> 2) If the router has any DHCP ability (they normally do), disable it.
>> >> Enable
>> >> DHCP on the SBS. Set all workstations to get IP's via DHCP from SBS.
>> >>
>> >> Sounds like we can forget everything that happened 5 years ago because
>> >> you
>> >> have re-installed the server. When this was done, did you 'restore' AD
>> >> from
>> >> the old box? migrate it? or simply throw away the old and fresh
>> >> install?
>> >> If
>> >> it's a fresh installation have the client machines been properly
>> >> introduced
>> >> to the new domain?
>> >>
>> >> "tlc_13200@hotmail.com" <tlc13200hotmailcom@discussions.microsoft.com>
>> >> wrote
>> >> in message news:D35E15A3-EF04-48B6-9693-925A8EE12F84@microsoft.com...
>> >> >I have a client who is presently using SBS 2000, and is having
>> >> >constant
>> >> > problems with network connections. Here's what is happening. First,
>> >> > from
>> >> > time to time he loses connections and has to restart all of his
>> >> > workstations,
>> >> > and even the server to get he connections back.
>> >> >
>> >> > (History)
>> >> > Now, it was setup by somebody else over 5 years ago. Recently, I
>> >> > rebulit
>> >> > him
>> >> > a new server and loaded back his operating system into it, to get
>> >> > him
>> >> > running. Except, his network is static IP's with internet through
>> >> > the
>> >> > same
>> >> > LAN adapter.
>> >> >
>> >> > What I like to do for him, to solve his problem, is to attach his
>> >> > second
>> >> > LAN
>> >> > adapter with a router, for the internet, either DHCP or static using
>> >> > NAT.
>> >> > Then, using a HUB attach all of his computers to the second LAN
>> >> > adater
>> >> > and
>> >> > configure it to log in each workstation statically. This way, he
>> >> > will
>> >> > not
>> >> > have these issues again!
>> >> >
>> >> > Is this a better choice, or is there something else as to why he is
>> >> > having
>> >> > all of these problems.
>> >> >
>> >> > What he has, is a DSL modem attached to a wired router, along with
>> >> > all
>> >> > his
>> >> > clients, and they are seeing the server and logging in and seeing
>> >> > the
>> >> > internet too.
>> >> >
>> >> > Please advise if NAT is a good suggestion, I believe he is logging
>> >> > into
>> >> > a
>> >> > Domain controller... not sure, but can find out.
>> >> >
>> >> > I appreciate any feedback on this topic!
>> >>
>> >>
>> >>
>>
>>
>>

tlc13200hotmailcom
Tue Mar 04 18:13:00 CST 2008

When you say, let SBS do it for me... are you referring about Active
Directory? I'm sorry, it's just that I am confused on what exactly you are
trying to get at...

I mean setting up the LAN adpater on the server to DHCP is easy, but will it
actually solve the problem that the customer is having?

"SuperGumby [SBS MVP]" wrote:

> The problem is not specifically due to whether or not SBS is doing DHCP. It
> is all about the proper configuration of networking.
>
> It is possible to manually configure properly. It is easier to let SBS do it
> for you.
>
> Throwing devices at the mix willy-nilly won't fix anything.
>
> "tlc_13200@hotmail.com" <tlc13200hotmailcom@discussions.microsoft.com> wrote
> in message news:F133BB91-7974-479E-9F64-63C966C00D5D@microsoft.com...
> > Sorry, I should have been more clear. They all have been logging on with a
> > static IP, instead of dynamic. (Fixed IP instead of DHCP). I know very
> > little
> > about SBS 2000, compared to 2003, etc. I remembered that NAT had be set in
> > order for Windows Server 2000 to route the "name address translation" for
> > both the internet and the workstations to exist together.
> >
> > But, you are telling me that I have to tell SBS 2000 to confire itself as
> > DHCP and the problems will go away?!
> >
> > They are still freezing up with connection issues, and have to constantly
> > reboot their workstations, and even the server in order for the software
> > to
> > work again, temporarily of course.
> >
> > I figured, if I get them a new router and HUB switch, and plug the router
> > into one LAN adapter, and the HUB into another, and tell SBS 2000 to work
> > it's NAT that it would operate without the system crashing.
> >
> > Tell me is it the server causing the problem by not being DHCP?
> >
> > "SuperGumby [SBS MVP]" wrote:
> >
> >> Without the current IPConfig from the server and a workstation it is hard
> >> to
> >> pass comment. However, _most_ network related problems occur because
> >> things
> >> do not happen in the manner SBS requires. The simplest way of fixing this
> >> is
> >> to allow SBS to be boss.
> >>
> >> The users are not going to be confused by a change from static to dynamic
> >> IP
> >> addressing, they don't even see this process. (NOTE: I was wondering what
> >> you meant by 'static logon'.)
> >>
> >> "tlc_13200@hotmail.com" <tlc13200hotmailcom@discussions.microsoft.com>
> >> wrote
> >> in message news:1E38080C-9978-4241-8114-F8A530252A3C@microsoft.com...
> >> > Hi SuperGumby,
> >> >
> >> > Thank you for jogging my memory. Actually, no miragation was performed.
> >> > All
> >> > that was done, was a installation and I believe there is an AD. I have
> >> > to
> >> > look at it of course.
> >> >
> >> > But, what I do know, everything is setup statically. No DHCP!
> >> >
> >> > I believe the scheme of IP addresses its behind is 192.168.16.xxx.
> >> >
> >> > However, the DSL modem is plugged into the LINKSys router, and they are
> >> > sharing the internet through it. When you say: "Enable DHCP on the SBS.
> >> > Set
> >> > all workstations to get IP's via DHCP from SBS", I was wondering...
> >> > would
> >> > it
> >> > be best to attach the workstations unto a wired HUB and attach it to
> >> > the
> >> > server, being that their router is failing at times, and program the
> >> > workstations that way?
> >> >
> >> > And configuring the workstations to log in dynamically might confused
> >> > their
> >> > printers they have. Which I believe is static. Although, they are HP
> >> > laser
> >> > printer, and inkjet.
> >> >
> >> > I feel that their network connections is failing at times, where they
> >> > lose
> >> > the communication between the workstation and server application. Which
> >> > is
> >> > DENTRIX. A medical software application.
> >> >
> >> > Would enabling SBS to DHCP really solve their problem?
> >> >
> >> >
> >> > "SuperGumby [SBS MVP]" wrote:
> >> >
> >> >> I'd probably try to get the current setup reliably working before
> >> >> implementing any change.
> >> >>
> >> >> 1) Post the current output from 'IPConfig /all' for both the server
> >> >> and
> >> >> one
> >> >> workstation.
> >> >> 2) If the router has any DHCP ability (they normally do), disable it.
> >> >> Enable
> >> >> DHCP on the SBS. Set all workstations to get IP's via DHCP from SBS.
> >> >>
> >> >> Sounds like we can forget everything that happened 5 years ago because
> >> >> you
> >> >> have re-installed the server. When this was done, did you 'restore' AD
> >> >> from
> >> >> the old box? migrate it? or simply throw away the old and fresh
> >> >> install?
> >> >> If
> >> >> it's a fresh installation have the client machines been properly
> >> >> introduced
> >> >> to the new domain?
> >> >>
> >> >> "tlc_13200@hotmail.com" <tlc13200hotmailcom@discussions.microsoft.com>
> >> >> wrote
> >> >> in message news:D35E15A3-EF04-48B6-9693-925A8EE12F84@microsoft.com...
> >> >> >I have a client who is presently using SBS 2000, and is having
> >> >> >constant
> >> >> > problems with network connections. Here's what is happening. First,
> >> >> > from
> >> >> > time to time he loses connections and has to restart all of his
> >> >> > workstations,
> >> >> > and even the server to get he connections back.
> >> >> >
> >> >> > (History)
> >> >> > Now, it was setup by somebody else over 5 years ago. Recently, I
> >> >> > rebulit
> >> >> > him
> >> >> > a new server and loaded back his operating system into it, to get
> >> >> > him
> >> >> > running. Except, his network is static IP's with internet through
> >> >> > the
> >> >> > same
> >> >> > LAN adapter.
> >> >> >
> >> >> > What I like to do for him, to solve his problem, is to attach his
> >> >> > second
> >> >> > LAN
> >> >> > adapter with a router, for the internet, either DHCP or static using
> >> >> > NAT.
> >> >> > Then, using a HUB attach all of his computers to the second LAN
> >> >> > adater
> >> >> > and
> >> >> > configure it to log in each workstation statically. This way, he
> >> >> > will
> >> >> > not
> >> >> > have these issues again!
> >> >> >
> >> >> > Is this a better choice, or is there something else as to why he is
> >> >> > having
> >> >> > all of these problems.
> >> >> >
> >> >> > What he has, is a DSL modem attached to a wired router, along with
> >> >> > all
> >> >> > his
> >> >> > clients, and they are seeing the server and logging in and seeing
> >> >> > the
> >> >> > internet too.
> >> >> >
> >> >> > Please advise if NAT is a good suggestion, I believe he is logging
> >> >> > into
> >> >> > a
> >> >> > Domain controller... not sure, but can find out.
> >> >> >
> >> >> > I appreciate any feedback on this topic!
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>

SuperGumby
Tue Mar 04 18:22:12 CST 2008

NO, I am not talking about AD, I am talking about DHCP, I thought you were
too.

I cannot put it more plainly. Configure SBS's NIC for operation on a static
IP. Install and configure (using SBS wizards) the DHCP Server service on
SBS. Ensure no other DHCP source exists on the SBS network segment.
Configure all client PC's to get IP via DHCP.

"tlc_13200@hotmail.com" <tlc13200hotmailcom@discussions.microsoft.com> wrote
in message news:B7EBD4C8-A05E-45A7-B1BE-913DDFB69F55@microsoft.com...
> When you say, let SBS do it for me... are you referring about Active
> Directory? I'm sorry, it's just that I am confused on what exactly you are
> trying to get at...
>
> I mean setting up the LAN adpater on the server to DHCP is easy, but will
> it
> actually solve the problem that the customer is having?
>
> "SuperGumby [SBS MVP]" wrote:
>
>> The problem is not specifically due to whether or not SBS is doing DHCP.
>> It
>> is all about the proper configuration of networking.
>>
>> It is possible to manually configure properly. It is easier to let SBS do
>> it
>> for you.
>>
>> Throwing devices at the mix willy-nilly won't fix anything.
>>
>> "tlc_13200@hotmail.com" <tlc13200hotmailcom@discussions.microsoft.com>
>> wrote
>> in message news:F133BB91-7974-479E-9F64-63C966C00D5D@microsoft.com...
>> > Sorry, I should have been more clear. They all have been logging on
>> > with a
>> > static IP, instead of dynamic. (Fixed IP instead of DHCP). I know very
>> > little
>> > about SBS 2000, compared to 2003, etc. I remembered that NAT had be set
>> > in
>> > order for Windows Server 2000 to route the "name address translation"
>> > for
>> > both the internet and the workstations to exist together.
>> >
>> > But, you are telling me that I have to tell SBS 2000 to confire itself
>> > as
>> > DHCP and the problems will go away?!
>> >
>> > They are still freezing up with connection issues, and have to
>> > constantly
>> > reboot their workstations, and even the server in order for the
>> > software
>> > to
>> > work again, temporarily of course.
>> >
>> > I figured, if I get them a new router and HUB switch, and plug the
>> > router
>> > into one LAN adapter, and the HUB into another, and tell SBS 2000 to
>> > work
>> > it's NAT that it would operate without the system crashing.
>> >
>> > Tell me is it the server causing the problem by not being DHCP?
>> >
>> > "SuperGumby [SBS MVP]" wrote:
>> >
>> >> Without the current IPConfig from the server and a workstation it is
>> >> hard
>> >> to
>> >> pass comment. However, _most_ network related problems occur because
>> >> things
>> >> do not happen in the manner SBS requires. The simplest way of fixing
>> >> this
>> >> is
>> >> to allow SBS to be boss.
>> >>
>> >> The users are not going to be confused by a change from static to
>> >> dynamic
>> >> IP
>> >> addressing, they don't even see this process. (NOTE: I was wondering
>> >> what
>> >> you meant by 'static logon'.)
>> >>
>> >> "tlc_13200@hotmail.com" <tlc13200hotmailcom@discussions.microsoft.com>
>> >> wrote
>> >> in message news:1E38080C-9978-4241-8114-F8A530252A3C@microsoft.com...
>> >> > Hi SuperGumby,
>> >> >
>> >> > Thank you for jogging my memory. Actually, no miragation was
>> >> > performed.
>> >> > All
>> >> > that was done, was a installation and I believe there is an AD. I
>> >> > have
>> >> > to
>> >> > look at it of course.
>> >> >
>> >> > But, what I do know, everything is setup statically. No DHCP!
>> >> >
>> >> > I believe the scheme of IP addresses its behind is 192.168.16.xxx.
>> >> >
>> >> > However, the DSL modem is plugged into the LINKSys router, and they
>> >> > are
>> >> > sharing the internet through it. When you say: "Enable DHCP on the
>> >> > SBS.
>> >> > Set
>> >> > all workstations to get IP's via DHCP from SBS", I was wondering...
>> >> > would
>> >> > it
>> >> > be best to attach the workstations unto a wired HUB and attach it to
>> >> > the
>> >> > server, being that their router is failing at times, and program the
>> >> > workstations that way?
>> >> >
>> >> > And configuring the workstations to log in dynamically might
>> >> > confused
>> >> > their
>> >> > printers they have. Which I believe is static. Although, they are HP
>> >> > laser
>> >> > printer, and inkjet.
>> >> >
>> >> > I feel that their network connections is failing at times, where
>> >> > they
>> >> > lose
>> >> > the communication between the workstation and server application.
>> >> > Which
>> >> > is
>> >> > DENTRIX. A medical software application.
>> >> >
>> >> > Would enabling SBS to DHCP really solve their problem?
>> >> >
>> >> >
>> >> > "SuperGumby [SBS MVP]" wrote:
>> >> >
>> >> >> I'd probably try to get the current setup reliably working before
>> >> >> implementing any change.
>> >> >>
>> >> >> 1) Post the current output from 'IPConfig /all' for both the server
>> >> >> and
>> >> >> one
>> >> >> workstation.
>> >> >> 2) If the router has any DHCP ability (they normally do), disable
>> >> >> it.
>> >> >> Enable
>> >> >> DHCP on the SBS. Set all workstations to get IP's via DHCP from
>> >> >> SBS.
>> >> >>
>> >> >> Sounds like we can forget everything that happened 5 years ago
>> >> >> because
>> >> >> you
>> >> >> have re-installed the server. When this was done, did you 'restore'
>> >> >> AD
>> >> >> from
>> >> >> the old box? migrate it? or simply throw away the old and fresh
>> >> >> install?
>> >> >> If
>> >> >> it's a fresh installation have the client machines been properly
>> >> >> introduced
>> >> >> to the new domain?
>> >> >>
>> >> >> "tlc_13200@hotmail.com"
>> >> >> <tlc13200hotmailcom@discussions.microsoft.com>
>> >> >> wrote
>> >> >> in message
>> >> >> news:D35E15A3-EF04-48B6-9693-925A8EE12F84@microsoft.com...
>> >> >> >I have a client who is presently using SBS 2000, and is having
>> >> >> >constant
>> >> >> > problems with network connections. Here's what is happening.
>> >> >> > First,
>> >> >> > from
>> >> >> > time to time he loses connections and has to restart all of his
>> >> >> > workstations,
>> >> >> > and even the server to get he connections back.
>> >> >> >
>> >> >> > (History)
>> >> >> > Now, it was setup by somebody else over 5 years ago. Recently, I
>> >> >> > rebulit
>> >> >> > him
>> >> >> > a new server and loaded back his operating system into it, to get
>> >> >> > him
>> >> >> > running. Except, his network is static IP's with internet through
>> >> >> > the
>> >> >> > same
>> >> >> > LAN adapter.
>> >> >> >
>> >> >> > What I like to do for him, to solve his problem, is to attach his
>> >> >> > second
>> >> >> > LAN
>> >> >> > adapter with a router, for the internet, either DHCP or static
>> >> >> > using
>> >> >> > NAT.
>> >> >> > Then, using a HUB attach all of his computers to the second LAN
>> >> >> > adater
>> >> >> > and
>> >> >> > configure it to log in each workstation statically. This way, he
>> >> >> > will
>> >> >> > not
>> >> >> > have these issues again!
>> >> >> >
>> >> >> > Is this a better choice, or is there something else as to why he
>> >> >> > is
>> >> >> > having
>> >> >> > all of these problems.
>> >> >> >
>> >> >> > What he has, is a DSL modem attached to a wired router, along
>> >> >> > with
>> >> >> > all
>> >> >> > his
>> >> >> > clients, and they are seeing the server and logging in and seeing
>> >> >> > the
>> >> >> > internet too.
>> >> >> >
>> >> >> > Please advise if NAT is a good suggestion, I believe he is
>> >> >> > logging
>> >> >> > into
>> >> >> > a
>> >> >> > Domain controller... not sure, but can find out.
>> >> >> >
>> >> >> > I appreciate any feedback on this topic!
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>

tlc13200hotmailcom
Tue Mar 04 18:32:00 CST 2008

DHCP... there is a wizard in SBS 2000? Interesting... okay. So, I configue
the NIC's for operation on a STATIC IP? Like 192.168.16.xxx? Because what you
said below is to configure the NIC card that way, which it is already. Then
you said to Install & configure DHCP Server on SBS. And no, there isn't any
existing DHCP on it!

But why is the application still crashing when trying to access it? In other
words, what is it that STATIC IP is doing that DHCP would not do? How does
changing it really resolve the crashing issue?!

Can you explain?

"SuperGumby [SBS MVP]" wrote:

> NO, I am not talking about AD, I am talking about DHCP, I thought you were
> too.
>
> I cannot put it more plainly. Configure SBS's NIC for operation on a static
> IP. Install and configure (using SBS wizards) the DHCP Server service on
> SBS. Ensure no other DHCP source exists on the SBS network segment.
> Configure all client PC's to get IP via DHCP.
>
> "tlc_13200@hotmail.com" <tlc13200hotmailcom@discussions.microsoft.com> wrote
> in message news:B7EBD4C8-A05E-45A7-B1BE-913DDFB69F55@microsoft.com...
> > When you say, let SBS do it for me... are you referring about Active
> > Directory? I'm sorry, it's just that I am confused on what exactly you are
> > trying to get at...
> >
> > I mean setting up the LAN adpater on the server to DHCP is easy, but will
> > it
> > actually solve the problem that the customer is having?
> >
> > "SuperGumby [SBS MVP]" wrote:
> >
> >> The problem is not specifically due to whether or not SBS is doing DHCP.
> >> It
> >> is all about the proper configuration of networking.
> >>
> >> It is possible to manually configure properly. It is easier to let SBS do
> >> it
> >> for you.
> >>
> >> Throwing devices at the mix willy-nilly won't fix anything.
> >>
> >> "tlc_13200@hotmail.com" <tlc13200hotmailcom@discussions.microsoft.com>
> >> wrote
> >> in message news:F133BB91-7974-479E-9F64-63C966C00D5D@microsoft.com...
> >> > Sorry, I should have been more clear. They all have been logging on
> >> > with a
> >> > static IP, instead of dynamic. (Fixed IP instead of DHCP). I know very
> >> > little
> >> > about SBS 2000, compared to 2003, etc. I remembered that NAT had be set
> >> > in
> >> > order for Windows Server 2000 to route the "name address translation"
> >> > for
> >> > both the internet and the workstations to exist together.
> >> >
> >> > But, you are telling me that I have to tell SBS 2000 to confire itself
> >> > as
> >> > DHCP and the problems will go away?!
> >> >
> >> > They are still freezing up with connection issues, and have to
> >> > constantly
> >> > reboot their workstations, and even the server in order for the
> >> > software
> >> > to
> >> > work again, temporarily of course.
> >> >
> >> > I figured, if I get them a new router and HUB switch, and plug the
> >> > router
> >> > into one LAN adapter, and the HUB into another, and tell SBS 2000 to
> >> > work
> >> > it's NAT that it would operate without the system crashing.
> >> >
> >> > Tell me is it the server causing the problem by not being DHCP?
> >> >
> >> > "SuperGumby [SBS MVP]" wrote:
> >> >
> >> >> Without the current IPConfig from the server and a workstation it is
> >> >> hard
> >> >> to
> >> >> pass comment. However, _most_ network related problems occur because
> >> >> things
> >> >> do not happen in the manner SBS requires. The simplest way of fixing
> >> >> this
> >> >> is
> >> >> to allow SBS to be boss.
> >> >>
> >> >> The users are not going to be confused by a change from static to
> >> >> dynamic
> >> >> IP
> >> >> addressing, they don't even see this process. (NOTE: I was wondering
> >> >> what
> >> >> you meant by 'static logon'.)
> >> >>
> >> >> "tlc_13200@hotmail.com" <tlc13200hotmailcom@discussions.microsoft.com>
> >> >> wrote
> >> >> in message news:1E38080C-9978-4241-8114-F8A530252A3C@microsoft.com...
> >> >> > Hi SuperGumby,
> >> >> >
> >> >> > Thank you for jogging my memory. Actually, no miragation was
> >> >> > performed.
> >> >> > All
> >> >> > that was done, was a installation and I believe there is an AD. I
> >> >> > have
> >> >> > to
> >> >> > look at it of course.
> >> >> >
> >> >> > But, what I do know, everything is setup statically. No DHCP!
> >> >> >
> >> >> > I believe the scheme of IP addresses its behind is 192.168.16.xxx.
> >> >> >
> >> >> > However, the DSL modem is plugged into the LINKSys router, and they
> >> >> > are
> >> >> > sharing the internet through it. When you say: "Enable DHCP on the
> >> >> > SBS.
> >> >> > Set
> >> >> > all workstations to get IP's via DHCP from SBS", I was wondering...
> >> >> > would
> >> >> > it
> >> >> > be best to attach the workstations unto a wired HUB and attach it to
> >> >> > the
> >> >> > server, being that their router is failing at times, and program the
> >> >> > workstations that way?
> >> >> >
> >> >> > And configuring the workstations to log in dynamically might
> >> >> > confused
> >> >> > their
> >> >> > printers they have. Which I believe is static. Although, they are HP
> >> >> > laser
> >> >> > printer, and inkjet.
> >> >> >
> >> >> > I feel that their network connections is failing at times, where
> >> >> > they
> >> >> > lose
> >> >> > the communication between the workstation and server application.
> >> >> > Which
> >> >> > is
> >> >> > DENTRIX. A medical software application.
> >> >> >
> >> >> > Would enabling SBS to DHCP really solve their problem?
> >> >> >
> >> >> >
> >> >> > "SuperGumby [SBS MVP]" wrote:
> >> >> >
> >> >> >> I'd probably try to get the current setup reliably working before
> >> >> >> implementing any change.
> >> >> >>
> >> >> >> 1) Post the current output from 'IPConfig /all' for both the server
> >> >> >> and
> >> >> >> one
> >> >> >> workstation.
> >> >> >> 2) If the router has any DHCP ability (they normally do), disable
> >> >> >> it.
> >> >> >> Enable
> >> >> >> DHCP on the SBS. Set all workstations to get IP's via DHCP from
> >> >> >> SBS.
> >> >> >>
> >> >> >> Sounds like we can forget everything that happened 5 years ago
> >> >> >> because
> >> >> >> you
> >> >> >> have re-installed the server. When this was done, did you 'restore'
> >> >> >> AD
> >> >> >> from
> >> >> >> the old box? migrate it? or simply throw away the old and fresh
> >> >> >> install?
> >> >> >> If
> >> >> >> it's a fresh installation have the client machines been properly
> >> >> >> introduced
> >> >> >> to the new domain?
> >> >> >>
> >> >> >> "tlc_13200@hotmail.com"
> >> >> >> <tlc13200hotmailcom@discussions.microsoft.com>
> >> >> >> wrote
> >> >> >> in message
> >> >> >> news:D35E15A3-EF04-48B6-9693-925A8EE12F84@microsoft.com...
> >> >> >> >I have a client who is presently using SBS 2000, and is having
> >> >> >> >constant
> >> >> >> > problems with network connections. Here's what is happening.
> >> >> >> > First,
> >> >> >> > from
> >> >> >> > time to time he loses connections and has to restart all of his
> >> >> >> > workstations,
> >> >> >> > and even the server to get he connections back.
> >> >> >> >
> >> >> >> > (History)
> >> >> >> > Now, it was setup by somebody else over 5 years ago. Recently, I
> >> >> >> > rebulit
> >> >> >> > him
> >> >> >> > a new server and loaded back his operating system into it, to get
> >> >> >> > him
> >> >> >> > running. Except, his network is static IP's with internet through
> >> >> >> > the
> >> >> >> > same
> >> >> >> > LAN adapter.
> >> >> >> >
> >> >> >> > What I like to do for him, to solve his problem, is to attach his
> >> >> >> > second
> >> >> >> > LAN
> >> >> >> > adapter with a router, for the internet, either DHCP or static
> >> >> >> > using
> >> >> >> > NAT.
> >> >> >> > Then, using a HUB attach all of his computers to the second LAN
> >> >> >> > adater
> >> >> >> > and
> >> >> >> > configure it to log in each workstation statically. This way, he
> >> >> >> > will
> >> >> >> > not
> >> >> >> > have these issues again!
> >> >> >> >
> >> >> >> > Is this a better choice, or is there something else as to why he
> >> >> >> > is
> >> >> >> > having
> >> >> >> > all of these problems.
> >> >> >> >
> >> >> >> > What he has, is a DSL modem attached to a wired router, along
> >> >> >> > with
> >> >> >> > all
> >> >> >> > his
> >> >> >> > clients, and they are seeing the server and logging in and seeing
> >> >> >> > the
> >> >> >> > internet too.
> >> >> >> >
> >> >> >> > Please advise if NAT is a good suggestion, I believe he is
> >> >> >> > logging
> >> >> >> > into
> >> >> >> > a
> >> >> >> > Domain controller... not sure, but can find out.
> >> >> >> >
> >> >> >> > I appreciate any feedback on this topic!
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>

Merv
Wed Mar 05 12:34:03 CST 2008

SBS 2000, 2 NICs, STATIC IP, ISA [PROXY SERVER], with ROUTER
http://www.sbslinks.com/sbs2000router.htm

Andy Goodman's articles on setting up SBS 2000
(SBS 2000 Walkthrough)
http://www.sbs-rocks.com/articles.htm#SBS 2000 Articles

Once you've got SBS 2000 set up correctly, if the apps continue to crash,
then you can start looking at hardware (maybe a NIC problem) or software
issues.

As a side note: If you only have a single NIC in the SBS 2000 server, then
ISA will be running in Cache mode and not Firewall mode.

--
Merv Porter [SBS-MVP]
============================

"tlc_13200@hotmail.com" <tlc13200hotmailcom@discussions.microsoft.com> wrote
in message news:BAC90061-E797-4701-8148-CC72675BECE2@microsoft.com...
> DHCP... there is a wizard in SBS 2000? Interesting... okay. So, I configue
> the NIC's for operation on a STATIC IP? Like 192.168.16.xxx? Because what
> you
> said below is to configure the NIC card that way, which it is already.
> Then
> you said to Install & configure DHCP Server on SBS. And no, there isn't
> any
> existing DHCP on it!
>
> But why is the application still crashing when trying to access it? In
> other
> words, what is it that STATIC IP is doing that DHCP would not do? How does
> changing it really resolve the crashing issue?!
>
> Can you explain?
>
> "SuperGumby [SBS MVP]" wrote:
>
>> NO, I am not talking about AD, I am talking about DHCP, I thought you
>> were
>> too.
>>
>> I cannot put it more plainly. Configure SBS's NIC for operation on a
>> static
>> IP. Install and configure (using SBS wizards) the DHCP Server service on
>> SBS. Ensure no othe