Re: Configuring SBS 2000 for NAT.
- From: tlc_13200@xxxxxxxxxxx <tlc13200hotmailcom@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 4 Mar 2008 14:52:01 -0800
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@xxxxxxxxxxx" <tlc13200hotmailcom@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message news:D35E15A3-EF04-48B6-9693-925A8EE12F84@xxxxxxxxxxxxxxxx
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!
- Follow-Ups:
- Re: Configuring SBS 2000 for NAT.
- From: SuperGumby [SBS MVP]
- Re: Configuring SBS 2000 for NAT.
- References:
- Re: Configuring SBS 2000 for NAT.
- From: SuperGumby [SBS MVP]
- Re: Configuring SBS 2000 for NAT.
- Prev by Date: Re: Microsoft Mobile Information Server question...
- Next by Date: Re: Configuring SBS 2000 for NAT.
- Previous by thread: Re: Configuring SBS 2000 for NAT.
- Next by thread: Re: Configuring SBS 2000 for NAT.
- Index(es):
Relevant Pages
|
Loading