Windows 2000 Server - Problems getting internet to clients

Hi all,

I am having bother with a small office network I manage. I am tec
savvy but am far from an advanced network guru. This one has got me
and I would appreciate your help.

Here is the setup.

Client/Server Domain style network.
1x Windows 2000 Server (dual NICs) with 5x XP Pro Clients
NIC#1 is on the motherboard (gigabit ethernet), NIC#2 is a PCI
-NIC#1 goes to a Linksys switch which has the 5 clients connected t
it. The clients have static IP addresses/not DHCP.
-NIC#2 -was- connected to a Linksys wireless ADSL router (with 4 por
switch) which was connected to the phone line //I can't remember ho
these IPs were allocated

We started experiencing internet problems...it was taking a long tim
to access any web pages, often with pages not coming up at all. Afte
contacting the (ADSL) ISP they wanted me to check our side of th
connections.

To cut a long story short, I replaced the router (got a Netgear one
can't remember the model sorry), server NIC card, and the RJ11 system.

I setup the router using its wizard to see that it all worked, and i
does. So the server now has internet. Getting the internet back to th
clients is not working though, I have fiddled about with the I
addresses, subnets, gateways etc but haven't got the solution.
clearly haven't got the right one, and as I said, this is a bit out o
my depth. The clients can't ping the router.

Next time I am at work I can get all the IP addresses for you of th
machines etc so you can better advise, but thought there would be som
of you who would know exactly what my problem is.

Myself and a friend have spent a lot of time trying to get this to wor
already, with much googling going on as well, but have come to a dea
end and need some help.


General advice would be much appreciated. The person who helped m
install the network initially recommended we use the 2 NIC setup, bu
if you have any other recommendations I am all ears.

Also, the Netgear router has a firewall in it, is it ok to relay on? o
should I get good firewall software for the server? or a seperat
hardware firewall entirely?

Thanks in advance for your help,

Hope you are enjoying the festive period

Iai

--
iai
-----------------------------------------------------------------------
iain's Profile: http://forums.techarena.in/member.php?userid=3842
View this thread: http://forums.techarena.in/showthread.php?t=88052

http://forums.techarena.i

* iain (Sat, 29 Dec 2007 19:55:02 +0530)
> I am having bother with a small office network I manage. I am tech
> savvy but am far from an advanced network guru. This one has got me,
> and I would appreciate your help.
>
> Here is the setup.
>
> Client/Server Domain style network.
> 1x Windows 2000 Server (dual NICs) with 5x XP Pro Clients
> NIC#1 is on the motherboard (gigabit ethernet), NIC#2 is a PCI
> -NIC#1 goes to a Linksys switch which has the 5 clients connected to
> it. The clients have static IP addresses/not DHCP.
> -NIC#2 -was- connected to a Linksys wireless ADSL router (with 4 port
> switch) which was connected to the phone line //I can't remember how
> these IPs were allocated
>
> We started experiencing internet problems...it was taking a long time
> to access any web pages, often with pages not coming up at all. After
> contacting the (ADSL) ISP they wanted me to check our side of the
> connections.
>
> To cut a long story short, I replaced the router (got a Netgear one,
> can't remember the model sorry), server NIC card, and the RJ11 system.
>
> I setup the router using its wizard to see that it all worked, and it
> does. So the server now has internet. Getting the internet back to the
> clients is not working though, I have fiddled about with the IP
> addresses, subnets, gateways etc but haven't got the solution. I
> clearly haven't got the right one, and as I said, this is a bit out of
> my depth. The clients can't ping the router.
>
> Next time I am at work I can get all the IP addresses for you of the
> machines etc so you can better advise, but thought there would be some
> of you who would know exactly what my problem is.
>
> Myself and a friend have spent a lot of time trying to get this to work
> already, with much googling going on as well, but have come to a dead
> end and need some help.
>
> General advice would be much appreciated. The person who helped me
> install the network initially recommended we use the 2 NIC setup, but
> if you have any other recommendations I am all ears.

First: this is basic tech stuff and not "advanced networking". So the
next time - before you and your friend "spend a lot of time getting
this to work" - you should let someone "tech savy" do the work (no
offence).

As far as I understand your problem /was/ slow internet access and now
it is that the clients can't access the internet at all?

First check that the clients are in the same subnet as the internal
NIC of the server. Can they ping the server? Check if the server can
ping the router and the internet. Check that the external NIC of the
server is on the same subnet as the internal NIC of the router. Check
if the server does routing:

* How To Enable TCP/IP Forwarding in Windows Server 2003
http://support.microsoft.com/kb/323339/en-us


Thorsten

To be frank, that is not a sensible way to run your network. There is
really no reason to use your DC as a router when you have a device specially
built to do that for you. Running a DC with two NICs has been a problem
since NT days and it still is. Microsoft recommends that you do not
multihome a DC. The only exception is SBS which is designed to work that
way.

I would just use one NIC in the server and put it on the same hub/switch
as the client machines. If the Netgear has enough ports you can plug them
all directly into that. Switch off the DHCP function on the Netgear and run
DHCP on the server ( or just configure the clients manually, as you will for
the server). All machines, including the DC, use the router as their default
gateway but use the DC for DNS. (This is essential for AD to work properly.
DNS was probably the reason for you past problems).

If you haven't already done so, you also need to modify your local DNS
to forward to an external DNS service or to your ADSL router. (Mine works OK
if I forward DNS to 10.1.1.1, which is my D-Link ADSL router, but will also
work if I set it to forward directly to the DNS server at my ISP).

If you have not used DNS forwarding before, note that it may be disabled
in W2k. You need to delete the . at the top of the DNS tree to use
forwarding.

Briefly you will have a single network with machines all in the same
subnet using the Netgear as the gateway. All machines will use the DC for
DNS to resolve both local and foreign names and URLs. eg

Internet
|
public IP
Netgear
10.1.1.1
|
DC
10.1.1.21 dg 10.1.1.1
dns 10.1..21
|
|
workstations
10.1.1 x dg 10.1.1.1
dns 10.1.1.21

"iain" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> Hi all,
>
> I am having bother with a small office network I manage. I am tech
> savvy but am far from an advanced network guru. This one has got me,
> and I would appreciate your help.
>
> Here is the setup.
>
> Client/Server Domain style network.
> 1x Windows 2000 Server (dual NICs) with 5x XP Pro Clients
> NIC#1 is on the motherboard (gigabit ethernet), NIC#2 is a PCI
> -NIC#1 goes to a Linksys switch which has the 5 clients connected to
> it. The clients have static IP addresses/not DHCP.
> -NIC#2 -was- connected to a Linksys wireless ADSL router (with 4 port
> switch) which was connected to the phone line //I can't remember how
> these IPs were allocated
>
> We started experiencing internet problems...it was taking a long time
> to access any web pages, often with pages not coming up at all. After
> contacting the (ADSL) ISP they wanted me to check our side of the
> connections.
>
> To cut a long story short, I replaced the router (got a Netgear one,
> can't remember the model sorry), server NIC card, and the RJ11 system.
>
> I setup the router using its wizard to see that it all worked, and it
> does. So the server now has internet. Getting the internet back to the
> clients is not working though, I have fiddled about with the IP
> addresses, subnets, gateways etc but haven't got the solution. I
> clearly haven't got the right one, and as I said, this is a bit out of
> my depth. The clients can't ping the router.
>
> Next time I am at work I can get all the IP addresses for you of the
> machines etc so you can better advise, but thought there would be some
> of you who would know exactly what my problem is.
>
> Myself and a friend have spent a lot of time trying to get this to work
> already, with much googling going on as well, but have come to a dead
> end and need some help.
>
>
> General advice would be much appreciated. The person who helped me
> install the network initially recommended we use the 2 NIC setup, but
> if you have any other recommendations I am all ears.
>
> Also, the Netgear router has a firewall in it, is it ok to relay on? or
> should I get good firewall software for the server? or a seperate
> hardware firewall entirely?
>
> Thanks in advance for your help,
>
> Hope you are enjoying the festive period
>
> Iain
>
>
> --
> iain
> ------------------------------------------------------------------------
> iain's Profile: http://forums.techarena.in/member.php?userid=38425
> View this thread: http://forums.techarena.in/showthread.php?t=880523
>
> http://forums.techarena.in
>

Bill,

Could you expound some on not using the dual NIC configuration?

I've got a brand new Dell Poweredge 2900 that has a dual NIC in it and I was
going to set each with their own IP address and set up as main DC.

Am I incorrect? It came from Dell that way?

Could you expound on the dual NIC issues?

Thanks in advance.

Mike

On 12/29/07 6:32 PM, in article (E-Mail Removed), "Bill
Grant" <not.available@online> wrote:

> To be frank, that is not a sensible way to run your network. There is
> really no reason to use your DC as a router when you have a device specially
> built to do that for you. Running a DC with two NICs has been a problem
> since NT days and it still is. Microsoft recommends that you do not
> multihome a DC. The only exception is SBS which is designed to work that
> way.
>
> I would just use one NIC in the server and put it on the same hub/switch
> as the client machines. If the Netgear has enough ports you can plug them
> all directly into that. Switch off the DHCP function on the Netgear and run
> DHCP on the server ( or just configure the clients manually, as you will for
> the server). All machines, including the DC, use the router as their default
> gateway but use the DC for DNS. (This is essential for AD to work properly.
> DNS was probably the reason for you past problems).
>
> If you haven't already done so, you also need to modify your local DNS
> to forward to an external DNS service or to your ADSL router. (Mine works OK
> if I forward DNS to 10.1.1.1, which is my D-Link ADSL router, but will also
> work if I set it to forward directly to the DNS server at my ISP).
>
> If you have not used DNS forwarding before, note that it may be disabled
> in W2k. You need to delete the . at the top of the DNS tree to use
> forwarding.
>
> Briefly you will have a single network with machines all in the same
> subnet using the Netgear as the gateway. All machines will use the DC for
> DNS to resolve both local and foreign names and URLs. eg
>
> Internet
> |
> public IP
> Netgear
> 10.1.1.1
> |
> DC
> 10.1.1.21 dg 10.1.1.1
> dns 10.1..21
> |
> |
> workstations
> 10.1.1 x dg 10.1.1.1
> dns 10.1.1.21
>
> "iain" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>
>> Hi all,
>>
>> I am having bother with a small office network I manage. I am tech
>> savvy but am far from an advanced network guru. This one has got me,
>> and I would appreciate your help.
>>
>> Here is the setup.
>>
>> Client/Server Domain style network.
>> 1x Windows 2000 Server (dual NICs) with 5x XP Pro Clients
>> NIC#1 is on the motherboard (gigabit ethernet), NIC#2 is a PCI
>> -NIC#1 goes to a Linksys switch which has the 5 clients connected to
>> it. The clients have static IP addresses/not DHCP.
>> -NIC#2 -was- connected to a Linksys wireless ADSL router (with 4 port
>> switch) which was connected to the phone line //I can't remember how
>> these IPs were allocated
>>
>> We started experiencing internet problems...it was taking a long time
>> to access any web pages, often with pages not coming up at all. After
>> contacting the (ADSL) ISP they wanted me to check our side of the
>> connections.
>>
>> To cut a long story short, I replaced the router (got a Netgear one,
>> can't remember the model sorry), server NIC card, and the RJ11 system.
>>
>> I setup the router using its wizard to see that it all worked, and it
>> does. So the server now has internet. Getting the internet back to the
>> clients is not working though, I have fiddled about with the IP
>> addresses, subnets, gateways etc but haven't got the solution. I
>> clearly haven't got the right one, and as I said, this is a bit out of
>> my depth. The clients can't ping the router.
>>
>> Next time I am at work I can get all the IP addresses for you of the
>> machines etc so you can better advise, but thought there would be some
>> of you who would know exactly what my problem is.
>>
>> Myself and a friend have spent a lot of time trying to get this to work
>> already, with much googling going on as well, but have come to a dead
>> end and need some help.
>>
>>
>> General advice would be much appreciated. The person who helped me
>> install the network initially recommended we use the 2 NIC setup, but
>> if you have any other recommendations I am all ears.
>>
>> Also, the Netgear router has a firewall in it, is it ok to relay on? or
>> should I get good firewall software for the server? or a seperate
>> hardware firewall entirely?
>>
>> Thanks in advance for your help,
>>
>> Hope you are enjoying the festive period
>>
>> Iain
>>
>>
>> --
>> iain
>> ------------------------------------------------------------------------
>> iain's Profile: http://forums.techarena.in/member.php?userid=38425
>> View this thread: http://forums.techarena.in/showthread.php?t=880523
>>
>> http://forums.techarena.in
>>
>

Just because a machine has two NICs, you don't have to use them. You can
simply disable one of them. I suspect that Dell has SBS in mind for that
config.

The basic problem with a DC having two NICs is that the machines then has
two IP addresses linked to its name. This can cause problems with the
browser service in particular, but can cause other odd problems. If the NICs
are identical you can use NIC teaming, so that the machine effectively only
has one IP address, but that is a different situation.

How were you planning to use two NICs? Using a DC as a router is not a
good idea. If you are not using it as a router, the two NICs would be in the
same IP subnet, and that is a no-no unless they are teamed.

"Michael Jarjoura" <(E-Mail Removed)> wrote in message
news:C39C9459.F904%(E-Mail Removed)...
> Bill,
>
> Could you expound some on not using the dual NIC configuration?
>
> I've got a brand new Dell Poweredge 2900 that has a dual NIC in it and I
> was
> going to set each with their own IP address and set up as main DC.
>
> Am I incorrect? It came from Dell that way?
>
> Could you expound on the dual NIC issues?
>
> Thanks in advance.
>
> Mike
>
> On 12/29/07 6:32 PM, in article (E-Mail Removed),
> "Bill
> Grant" <not.available@online> wrote:
>
>> To be frank, that is not a sensible way to run your network. There is
>> really no reason to use your DC as a router when you have a device
>> specially
>> built to do that for you. Running a DC with two NICs has been a problem
>> since NT days and it still is. Microsoft recommends that you do not
>> multihome a DC. The only exception is SBS which is designed to work that
>> way.
>>
>> I would just use one NIC in the server and put it on the same
>> hub/switch
>> as the client machines. If the Netgear has enough ports you can plug
>> them
>> all directly into that. Switch off the DHCP function on the Netgear and
>> run
>> DHCP on the server ( or just configure the clients manually, as you will
>> for
>> the server). All machines, including the DC, use the router as their
>> default
>> gateway but use the DC for DNS. (This is essential for AD to work
>> properly.
>> DNS was probably the reason for you past problems).
>>
>> If you haven't already done so, you also need to modify your local
>> DNS
>> to forward to an external DNS service or to your ADSL router. (Mine works
>> OK
>> if I forward DNS to 10.1.1.1, which is my D-Link ADSL router, but will
>> also
>> work if I set it to forward directly to the DNS server at my ISP).
>>
>> If you have not used DNS forwarding before, note that it may be
>> disabled
>> in W2k. You need to delete the . at the top of the DNS tree to use
>> forwarding.
>>
>> Briefly you will have a single network with machines all in the same
>> subnet using the Netgear as the gateway. All machines will use the DC for
>> DNS to resolve both local and foreign names and URLs. eg
>>
>> Internet
>> |
>> public IP
>> Netgear
>> 10.1.1.1
>> |
>> DC
>> 10.1.1.21 dg 10.1.1.1
>> dns 10.1..21
>> |
>> |
>> workstations
>> 10.1.1 x dg 10.1.1.1
>> dns 10.1.1.21
>>
>> "iain" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>>
>>> Hi all,
>>>
>>> I am having bother with a small office network I manage. I am tech
>>> savvy but am far from an advanced network guru. This one has got me,
>>> and I would appreciate your help.
>>>
>>> Here is the setup.
>>>
>>> Client/Server Domain style network.
>>> 1x Windows 2000 Server (dual NICs) with 5x XP Pro Clients
>>> NIC#1 is on the motherboard (gigabit ethernet), NIC#2 is a PCI
>>> -NIC#1 goes to a Linksys switch which has the 5 clients connected to
>>> it. The clients have static IP addresses/not DHCP.
>>> -NIC#2 -was- connected to a Linksys wireless ADSL router (with 4 port
>>> switch) which was connected to the phone line //I can't remember how
>>> these IPs were allocated
>>>
>>> We started experiencing internet problems...it was taking a long time
>>> to access any web pages, often with pages not coming up at all. After
>>> contacting the (ADSL) ISP they wanted me to check our side of the
>>> connections.
>>>
>>> To cut a long story short, I replaced the router (got a Netgear one,
>>> can't remember the model sorry), server NIC card, and the RJ11 system.
>>>
>>> I setup the router using its wizard to see that it all worked, and it
>>> does. So the server now has internet. Getting the internet back to the
>>> clients is not working though, I have fiddled about with the IP
>>> addresses, subnets, gateways etc but haven't got the solution. I
>>> clearly haven't got the right one, and as I said, this is a bit out of
>>> my depth. The clients can't ping the router.
>>>
>>> Next time I am at work I can get all the IP addresses for you of the
>>> machines etc so you can better advise, but thought there would be some
>>> of you who would know exactly what my problem is.
>>>
>>> Myself and a friend have spent a lot of time trying to get this to work
>>> already, with much googling going on as well, but have come to a dead
>>> end and need some help.
>>>
>>>
>>> General advice would be much appreciated. The person who helped me
>>> install the network initially recommended we use the 2 NIC setup, but
>>> if you have any other recommendations I am all ears.
>>>
>>> Also, the Netgear router has a firewall in it, is it ok to relay on? or
>>> should I get good firewall software for the server? or a seperate
>>> hardware firewall entirely?
>>>
>>> Thanks in advance for your help,
>>>
>>> Hope you are enjoying the festive period
>>>
>>> Iain
>>>
>>>
>>> --
>>> iain
>>> ------------------------------------------------------------------------
>>> iain's Profile: http://forums.techarena.in/member.php?userid=38425
>>> View this thread: http://forums.techarena.in/showthread.php?t=880523
>>>
>>> http://forums.techarena.in
>>>
>>
>
>

Thanks for all your input, it's much appreciated.

I will try setting it up as you have described Bill.

Regarding the firewall - is the one on the Netgear likely to b
sufficient or is more needed? Could you make any recommendations?

Thanks again,

Iain

Bill Grant;3415937 Wrote:
> To be frank, that is not a sensible way to run your network. There is
> really no reason to use your DC as a router when you have a devic
> specially
> built to do that for you. Running a DC with two NICs has been
> problem
> since NT days and it still is. Microsoft recommends that you do not
> multihome a DC. The only exception is SBS which is designed to wor
> that
> way.
>
> I would just use one NIC in the server and put it on the sam
> hub/switch
> as the client machines. If the Netgear has enough ports you can plu
> them
> all directly into that. Switch off the DHCP function on the Netgear an
> run
> DHCP on the server ( or just configure the clients manually, as yo
> will for
> the server). All machines, including the DC, use the router as thei
> default
> gateway but use the DC for DNS. (This is essential for AD to wor
> properly.
> DNS was probably the reason for you past problems).
>
> If you haven't already done so, you also need to modify your local DNS
> to forward to an external DNS service or to your ADSL router. (Min
> works OK
> if I forward DNS to 10.1.1.1, which is my D-Link ADSL router, but wil
> also
> work if I set it to forward directly to the DNS server at my ISP).
>
> If you have not used DNS forwarding before, note that it may b
> disabled
> in W2k. You need to delete the . at the top of the DNS tree to use
> forwarding.
>
> Briefly you will have a single network with machines all in the same
> subnet using the Netgear as the gateway. All machines will use the D
> for
> DNS to resolve both local and foreign names and URLs. eg
>
> Internet
> |
> public IP
> Netgear
> 10.1.1.1
> |
> DC
> 10.1.1.21 dg 10.1.1.1
> dns 10.1..21
> |
> |
> workstations
> 10.1.1 x dg 10.1.1.1
> dns 10.1.1.21
>
> "iain" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> >
> > Hi all,
> >
> > I am having bother with a small office network I manage. I am tech
> > savvy but am far from an advanced network guru. This one has got me,
> > and I would appreciate your help.
> >
> > Here is the setup.
> >
> > Client/Server Domain style network.
> > 1x Windows 2000 Server (dual NICs) with 5x XP Pro Clients
> > NIC#1 is on the motherboard (gigabit ethernet), NIC#2 is a PCI
> > -NIC#1 goes to a Linksys switch which has the 5 clients connected to
> > it. The clients have static IP addresses/not DHCP.
> > -NIC#2 -was- connected to a Linksys wireless ADSL router (with
> port
> > switch) which was connected to the phone line //I can't remembe
> how
> > these IPs were allocated
> >
> > We started experiencing internet problems...it was taking a lon
> time
> > to access any web pages, often with pages not coming up at all
> After
> > contacting the (ADSL) ISP they wanted me to check our side of the
> > connections.
> >
> > To cut a long story short, I replaced the router (got a Netgear one,
> > can't remember the model sorry), server NIC card, and the RJ1
> system.
> >
> > I setup the router using its wizard to see that it all worked, an
> it
> > does. So the server now has internet. Getting the internet back t
> the
> > clients is not working though, I have fiddled about with the IP
> > addresses, subnets, gateways etc but haven't got the solution. I
> > clearly haven't got the right one, and as I said, this is a bit ou
> of
> > my depth. The clients can't ping the router.
> >
> > Next time I am at work I can get all the IP addresses for you of the
> > machines etc so you can better advise, but thought there would b
> some
> > of you who would know exactly what my problem is.
> >
> > Myself and a friend have spent a lot of time trying to get this t
> work
> > already, with much googling going on as well, but have come to
> dead
> > end and need some help.
> >
> >
> > General advice would be much appreciated. The person who helped me
> > install the network initially recommended we use the 2 NIC setup,
> but
> > if you have any other recommendations I am all ears.
> >
> > Also, the Netgear router has a firewall in it, is it ok to relay on?
> or
> > should I get good firewall software for the server? or a seperate
> > hardware firewall entirely?
> >
> > Thanks in advance for your help,
> >
> > Hope you are enjoying the festive period
> >
> > Iain
> >
> >
> > --
> > iain
> >
> ------------------------------------------------------------------------
> > iain's Profile: http://forums.techarena.in/member.php?userid=38425
> > View this thread: http://forums.techarena.in/showthread.php?t=880523
> >
> > http://forums.techarena.in
> >


--
iain
------------------------------------------------------------------------
iain's Profile: http://forums.techarena.in/member.php?userid=38425
View this thread: http://forums.techarena.in/showthread.php?t=880523

http://forums.techarena.in

Thanks Bill,

I will contact Dell and see why they did a dual NIC configuration. I am
very green at network administration and am learning as I go each step.

Thanks, Mike



On 12/30/07 12:51 AM, in article #(E-Mail Removed), "Bill
Grant" <not.available@online> wrote:

> Just because a machine has two NICs, you don't have to use them. You can
> simply disable one of them. I suspect that Dell has SBS in mind for that
> config.
>
> The basic problem with a DC having two NICs is that the machines then has
> two IP addresses linked to its name. This can cause problems with the
> browser service in particular, but can cause other odd problems. If the NICs
> are identical you can use NIC teaming, so that the machine effectively only
> has one IP address, but that is a different situation.
>
> How were you planning to use two NICs? Using a DC as a router is not a
> good idea. If you are not using it as a router, the two NICs would be in the
> same IP subnet, and that is a no-no unless they are teamed.
>
> "Michael Jarjoura" <(E-Mail Removed)> wrote in message
> news:C39C9459.F904%(E-Mail Removed)...
>> Bill,
>>
>> Could you expound some on not using the dual NIC configuration?
>>
>> I've got a brand new Dell Poweredge 2900 that has a dual NIC in it and I
>> was
>> going to set each with their own IP address and set up as main DC.
>>
>> Am I incorrect? It came from Dell that way?
>>
>> Could you expound on the dual NIC issues?
>>
>> Thanks in advance.
>>
>> Mike
>>
>> On 12/29/07 6:32 PM, in article (E-Mail Removed),
>> "Bill
>> Grant" <not.available@online> wrote:
>>
>>> To be frank, that is not a sensible way to run your network. There is
>>> really no reason to use your DC as a router when you have a device
>>> specially
>>> built to do that for you. Running a DC with two NICs has been a problem
>>> since NT days and it still is. Microsoft recommends that you do not
>>> multihome a DC. The only exception is SBS which is designed to work that
>>> way.
>>>
>>> I would just use one NIC in the server and put it on the same
>>> hub/switch
>>> as the client machines. If the Netgear has enough ports you can plug
>>> them
>>> all directly into that. Switch off the DHCP function on the Netgear and
>>> run
>>> DHCP on the server ( or just configure the clients manually, as you will
>>> for
>>> the server). All machines, including the DC, use the router as their
>>> default
>>> gateway but use the DC for DNS. (This is essential for AD to work
>>> properly.
>>> DNS was probably the reason for you past problems).
>>>
>>> If you haven't already done so, you also need to modify your local
>>> DNS
>>> to forward to an external DNS service or to your ADSL router. (Mine works
>>> OK
>>> if I forward DNS to 10.1.1.1, which is my D-Link ADSL router, but will
>>> also
>>> work if I set it to forward directly to the DNS server at my ISP).
>>>
>>> If you have not used DNS forwarding before, note that it may be
>>> disabled
>>> in W2k. You need to delete the . at the top of the DNS tree to use
>>> forwarding.
>>>
>>> Briefly you will have a single network with machines all in the same
>>> subnet using the Netgear as the gateway. All machines will use the DC for
>>> DNS to resolve both local and foreign names and URLs. eg
>>>
>>> Internet
>>> |
>>> public IP
>>> Netgear
>>> 10.1.1.1
>>> |
>>> DC
>>> 10.1.1.21 dg 10.1.1.1
>>> dns 10.1..21
>>> |
>>> |
>>> workstations
>>> 10.1.1 x dg 10.1.1.1
>>> dns 10.1.1.21
>>>
>>> "iain" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>>
>>>> Hi all,
>>>>
>>>> I am having bother with a small office network I manage. I am tech
>>>> savvy but am far from an advanced network guru. This one has got me,
>>>> and I would appreciate your help.
>>>>
>>>> Here is the setup.
>>>>
>>>> Client/Server Domain style network.
>>>> 1x Windows 2000 Server (dual NICs) with 5x XP Pro Clients
>>>> NIC#1 is on the motherboard (gigabit ethernet), NIC#2 is a PCI
>>>> -NIC#1 goes to a Linksys switch which has the 5 clients connected to
>>>> it. The clients have static IP addresses/not DHCP.
>>>> -NIC#2 -was- connected to a Linksys wireless ADSL router (with 4 port
>>>> switch) which was connected to the phone line //I can't remember how
>>>> these IPs were allocated
>>>>
>>>> We started experiencing internet problems...it was taking a long time
>>>> to access any web pages, often with pages not coming up at all. After
>>>> contacting the (ADSL) ISP they wanted me to check our side of the
>>>> connections.
>>>>
>>>> To cut a long story short, I replaced the router (got a Netgear one,
>>>> can't remember the model sorry), server NIC card, and the RJ11 system.
>>>>
>>>> I setup the router using its wizard to see that it all worked, and it
>>>> does. So the server now has internet. Getting the internet back to the
>>>> clients is not working though, I have fiddled about with the IP
>>>> addresses, subnets, gateways etc but haven't got the solution. I
>>>> clearly haven't got the right one, and as I said, this is a bit out of
>>>> my depth. The clients can't ping the router.
>>>>
>>>> Next time I am at work I can get all the IP addresses for you of the
>>>> machines etc so you can better advise, but thought there would be some
>>>> of you who would know exactly what my problem is.
>>>>
>>>> Myself and a friend have spent a lot of time trying to get this to work
>>>> already, with much googling going on as well, but have come to a dead
>>>> end and need some help.
>>>>
>>>>
>>>> General advice would be much appreciated. The person who helped me
>>>> install the network initially recommended we use the 2 NIC setup, but
>>>> if you have any other recommendations I am all ears.
>>>>
>>>> Also, the Netgear router has a firewall in it, is it ok to relay on? or
>>>> should I get good firewall software for the server? or a seperate
>>>> hardware firewall entirely?
>>>>
>>>> Thanks in advance for your help,
>>>>
>>>> Hope you are enjoying the festive period
>>>>
>>>> Iain
>>>>
>>>>
>>>> --
>>>> iain
>>>> ------------------------------------------------------------------------
>>>> iain's Profile: http://forums.techarena.in/member.php?userid=38425
>>>> View this thread: http://forums.techarena.in/showthread.php?t=880523
>>>>
>>>> http://forums.techarena.in
>>>>
>>>
>>
>>
>