Problems getting internet to LAN pcs, Help!

Hello. I have searched for days to find a solution to this problem,
but i just can't seem to find one.

The Problem: Can't get internet to work on the LAN (I tried so many
things, none worked). On the connected PCs I get Error: Host

Not Accessable on Firefox. I also used Windows Live Messenger services
to diagnose and it comes up with "Gateway is Offline".

Physical Setup: Dynamic IP ISP > Linksys Router > Server 2003 > Switch
or PCs.

Done so far:
- Connected 1st NIC to the Linksys Router IP 192.168.1.105 (Internet
works on this Server computer)
- Installed 2nd NIC aka "The LAN" and set to static IP 192.168.0.1,
left Gateway and DNS empty
- Installed Domain Controller
- Installed Exchange 2003
- Configured DHCP (scope is 192.168.0.2 to 192.168.0.100, DNS to
192.168.0.1, 127.0.0.1)
- Configured DNS (used wizard to create forward lookup zone, setup
Fowarders to my ISP DNS (2 of them)
- Configured RRAS NAT (used the Wizard, set LAN nic to private and
Internet nic to Public without firewall)
- PCs are set to DHCP

Here is a few images of the settings I used just to give a better
visual:

>> http://www.systemweb.ca/temp/Diagram.JPG

I hope I wasn't too confusing, because im' confused and can't get
route internet to all the PCs connected to this computer.
Note: Some of the PCs have wireless NICs to test the routers internet
connection on that perticular PC, and it works.

All info and help is very much appreciated.



Havoc.

> - Installed 2nd NIC aka "The LAN" and set to static IP 192.168.0.1,
> left Gateway and DNS empty

Assuming this is the DC you put DNS on it should have it's own IP address on
it for DNS. Use the Actual IP address not 127.0.0.1

Point all AD clients to the DNS server you set up for the AD domain only.

hth
DDS

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> Hello. I have searched for days to find a solution to this problem,
> but i just can't seem to find one.
>
> The Problem: Can't get internet to work on the LAN (I tried so many
> things, none worked). On the connected PCs I get Error: Host
>
> Not Accessable on Firefox. I also used Windows Live Messenger services
> to diagnose and it comes up with "Gateway is Offline".
>
> Physical Setup: Dynamic IP ISP > Linksys Router > Server 2003 > Switch
> or PCs.
>
> Done so far:
> - Connected 1st NIC to the Linksys Router IP 192.168.1.105 (Internet
> works on this Server computer)
> - Installed 2nd NIC aka "The LAN" and set to static IP 192.168.0.1,
> left Gateway and DNS empty
> - Installed Domain Controller
> - Installed Exchange 2003
> - Configured DHCP (scope is 192.168.0.2 to 192.168.0.100, DNS to
> 192.168.0.1, 127.0.0.1)
> - Configured DNS (used wizard to create forward lookup zone, setup
> Fowarders to my ISP DNS (2 of them)
> - Configured RRAS NAT (used the Wizard, set LAN nic to private and
> Internet nic to Public without firewall)
> - PCs are set to DHCP
>
> Here is a few images of the settings I used just to give a better
> visual:
>
>>> http://www.systemweb.ca/temp/Diagram.JPG
>
> I hope I wasn't too confusing, because im' confused and can't get
> route internet to all the PCs connected to this computer.
> Note: Some of the PCs have wireless NICs to test the routers internet
> connection on that perticular PC, and it works.
>
> All info and help is very much appreciated.
>
>
>
> Havoc.
>

I am not sure why you decided to set your network up in that manner. Your
Linksys router is your connection to the Internet, but it is not in the same
subnet as your LAN machines. By setting up your server as a NAT router you
are effectively doing NAT twice - once at the server and again at the
router. In addition you have multihomed your DC, which is not a good thing
to do.

I would recommend that you do not run RRAS on your server. Put the
Linksys directly on the LAN, but disable its DHCP function. Run DHCP on the
server to allocate itself as DNS but the Linksys as default gateway. Set
your local DNS to forward to a public DNS service, so that it can resolve
external URLs as well as handle the local AD requirements. eg

Internet
|
public IP
Linksys
192.168.1.1
|
server
192.168.1.11 dg 192.168.1.1
| dns 192.168.1.11
workstations
192.168.1.x dg 192.168.1.1
dns 192.168.1.11

If you really want to stay with your current setup, I would recommend
that you do not run NAT on the server. Simply run it as a normal LAN router.
You will need to add extra routing to the Linksys so that it knows about the
internal subnet and how to reach it. eg

Internet
|
public IP
Linksys static route 192.168.0.0 255.255.255.0 192.168.1.105
192.168.1.1
|
192.168.1.105 dg 192.168.1.1
server
192.168.0.1 dg blank
|
workstations
192.168.0.x dg 192.168.0.1

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> Hello. I have searched for days to find a solution to this problem,
> but i just can't seem to find one.
>
> The Problem: Can't get internet to work on the LAN (I tried so many
> things, none worked). On the connected PCs I get Error: Host
>
> Not Accessable on Firefox. I also used Windows Live Messenger services
> to diagnose and it comes up with "Gateway is Offline".
>
> Physical Setup: Dynamic IP ISP > Linksys Router > Server 2003 > Switch
> or PCs.
>
> Done so far:
> - Connected 1st NIC to the Linksys Router IP 192.168.1.105 (Internet
> works on this Server computer)
> - Installed 2nd NIC aka "The LAN" and set to static IP 192.168.0.1,
> left Gateway and DNS empty
> - Installed Domain Controller
> - Installed Exchange 2003
> - Configured DHCP (scope is 192.168.0.2 to 192.168.0.100, DNS to
> 192.168.0.1, 127.0.0.1)
> - Configured DNS (used wizard to create forward lookup zone, setup
> Fowarders to my ISP DNS (2 of them)
> - Configured RRAS NAT (used the Wizard, set LAN nic to private and
> Internet nic to Public without firewall)
> - PCs are set to DHCP
>
> Here is a few images of the settings I used just to give a better
> visual:
>
>>> http://www.systemweb.ca/temp/Diagram.JPG
>
> I hope I wasn't too confusing, because im' confused and can't get
> route internet to all the PCs connected to this computer.
> Note: Some of the PCs have wireless NICs to test the routers internet
> connection on that perticular PC, and it works.
>
> All info and help is very much appreciated.
>
>
>
> Havoc.
>

You guys are right. I think someone messed me up the first time and
told me that all client PCs should be connected to the DC but I don't
think they new i had the router already.
This double NAT setup is definitly a problem, your idea makes a lot
more sense heh.

My only concern is if I do connect the server and clients to the
router, will I need to setup the DNS and DHCP on the server? I will
definitly need to use the AC for Exchange.. not sure how to go about
it.

Again, thanks for replies.

On Feb 26, 7:59 pm, "Bill Grant" <not.available@online> wrote:
> I am not sure why you decided to set your network up in that manner. Your
> Linksys router is your connection to the Internet, but it is not in the same
> subnet as your LAN machines. By setting up your server as a NAT router you
> are effectively doing NAT twice - once at the server and again at the
> router. In addition you have multihomed your DC, which is not a good thing
> to do.
>
> I would recommend that you do not run RRAS on your server. Put the
> Linksys directly on the LAN, but disable its DHCP function. Run DHCP on the
> server to allocate itself as DNS but the Linksys as default gateway. Set
> your local DNS to forward to a public DNS service, so that it can resolve
> external URLs as well as handle the local AD requirements. eg
>
> Internet
> |
> public IP
> Linksys
> 192.168.1.1
> |
> server
> 192.168.1.11 dg 192.168.1.1
> | dns 192.168.1.11
> workstations
> 192.168.1.x dg 192.168.1.1
> dns 192.168.1.11
>
> If you really want to stay with your current setup, I would recommend
> that you do not run NAT on the server. Simply run it as a normal LAN router.
> You will need to add extra routing to the Linksys so that it knows about the
> internal subnet and how to reach it. eg
>
> Internet
> |
> public IP
> Linksys static route 192.168.0.0 255.255.255.0 192.168.1.105
> 192.168.1.1
> |
> 192.168.1.105 dg 192.168.1.1
> server
> 192.168.0.1 dg blank
> |
> workstations
> 192.168.0.x dg 192.168.0.1
>
> <xoltrix2...@gmail.com> wrote in message
>
> news:(E-Mail Removed) ups.com...
>
> > Hello. I have searched for days to find a solution to this problem,
> > but i just can't seem to find one.
>
> > The Problem: Can't get internet to work on the LAN (I tried so many
> > things, none worked). On the connected PCs I get Error: Host
>
> > Not Accessable on Firefox. I also used Windows Live Messenger services
> > to diagnose and it comes up with "Gateway is Offline".
>
> > Physical Setup: Dynamic IP ISP > Linksys Router > Server 2003 > Switch
> > or PCs.
>
> > Done so far:
> > - Connected 1st NIC to the Linksys Router IP 192.168.1.105 (Internet
> > works on this Server computer)
> > - Installed 2nd NIC aka "The LAN" and set to static IP 192.168.0.1,
> > left Gateway and DNS empty
> > - Installed Domain Controller
> > - Installed Exchange 2003
> > - Configured DHCP (scope is 192.168.0.2 to 192.168.0.100, DNS to
> > 192.168.0.1, 127.0.0.1)
> > - Configured DNS (used wizard to create forward lookup zone, setup
> > Fowarders to my ISP DNS (2 of them)
> > - Configured RRAS NAT (used the Wizard, set LAN nic to private and
> > Internet nic to Public without firewall)
> > - PCs are set to DHCP
>
> > Here is a few images of the settings I used just to give a better
> > visual:
>
> >>>http://www.systemweb.ca/temp/Diagram.JPG
>
> > I hope I wasn't too confusing, because im' confused and can't get
> > route internet to all the PCs connected to this computer.
> > Note: Some of the PCs have wireless NICs to test the routers internet
> > connection on that perticular PC, and it works.
>
> > All info and help is very much appreciated.
>
> > Havoc.

You should be able to disable the DHCP function on the router and use DHCP
on the server. You need to use DNS on the server (because of AD). If you try
to use the router for DNS it will send requests to a public DNS server,
which won't have your AD info.

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> You guys are right. I think someone messed me up the first time and
> told me that all client PCs should be connected to the DC but I don't
> think they new i had the router already.
> This double NAT setup is definitly a problem, your idea makes a lot
> more sense heh.
>
> My only concern is if I do connect the server and clients to the
> router, will I need to setup the DNS and DHCP on the server? I will
> definitly need to use the AC for Exchange.. not sure how to go about
> it.
>
> Again, thanks for replies.
>
> On Feb 26, 7:59 pm, "Bill Grant" <not.available@online> wrote:
>> I am not sure why you decided to set your network up in that manner.
>> Your
>> Linksys router is your connection to the Internet, but it is not in the
>> same
>> subnet as your LAN machines. By setting up your server as a NAT router
>> you
>> are effectively doing NAT twice - once at the server and again at the
>> router. In addition you have multihomed your DC, which is not a good
>> thing
>> to do.
>>
>> I would recommend that you do not run RRAS on your server. Put the
>> Linksys directly on the LAN, but disable its DHCP function. Run DHCP on
>> the
>> server to allocate itself as DNS but the Linksys as default gateway. Set
>> your local DNS to forward to a public DNS service, so that it can resolve
>> external URLs as well as handle the local AD requirements. eg
>>
>> Internet
>> |
>> public IP
>> Linksys
>> 192.168.1.1
>> |
>> server
>> 192.168.1.11 dg 192.168.1.1
>> | dns 192.168.1.11
>> workstations
>> 192.168.1.x dg 192.168.1.1
>> dns 192.168.1.11
>>
>> If you really want to stay with your current setup, I would recommend
>> that you do not run NAT on the server. Simply run it as a normal LAN
>> router.
>> You will need to add extra routing to the Linksys so that it knows about
>> the
>> internal subnet and how to reach it. eg
>>
>> Internet
>> |
>> public IP
>> Linksys static route 192.168.0.0 255.255.255.0 192.168.1.105
>> 192.168.1.1
>> |
>> 192.168.1.105 dg 192.168.1.1
>> server
>> 192.168.0.1 dg blank
>> |
>> workstations
>> 192.168.0.x dg 192.168.0.1
>>
>> <xoltrix2...@gmail.com> wrote in message
>>
>> news:(E-Mail Removed) ups.com...
>>
>> > Hello. I have searched for days to find a solution to this problem,
>> > but i just can't seem to find one.
>>
>> > The Problem: Can't get internet to work on the LAN (I tried so many
>> > things, none worked). On the connected PCs I get Error: Host
>>
>> > Not Accessable on Firefox. I also used Windows Live Messenger services
>> > to diagnose and it comes up with "Gateway is Offline".
>>
>> > Physical Setup: Dynamic IP ISP > Linksys Router > Server 2003 > Switch
>> > or PCs.
>>
>> > Done so far:
>> > - Connected 1st NIC to the Linksys Router IP 192.168.1.105 (Internet
>> > works on this Server computer)
>> > - Installed 2nd NIC aka "The LAN" and set to static IP 192.168.0.1,
>> > left Gateway and DNS empty
>> > - Installed Domain Controller
>> > - Installed Exchange 2003
>> > - Configured DHCP (scope is 192.168.0.2 to 192.168.0.100, DNS to
>> > 192.168.0.1, 127.0.0.1)
>> > - Configured DNS (used wizard to create forward lookup zone, setup
>> > Fowarders to my ISP DNS (2 of them)
>> > - Configured RRAS NAT (used the Wizard, set LAN nic to private and
>> > Internet nic to Public without firewall)
>> > - PCs are set to DHCP
>>
>> > Here is a few images of the settings I used just to give a better
>> > visual:
>>
>> >>>http://www.systemweb.ca/temp/Diagram.JPG
>>
>> > I hope I wasn't too confusing, because im' confused and can't get
>> > route internet to all the PCs connected to this computer.
>> > Note: Some of the PCs have wireless NICs to test the routers internet
>> > connection on that perticular PC, and it works.
>>
>> > All info and help is very much appreciated.
>>
>> > Havoc.
>
>