Network Hardware

[Troy]

Hi!

I wrote the story below before I read PChuck's article "File Sharing On A
LAN With Two Routers" and now wonder whether or not to send this message as
File Sharing and Remote Connection are two tasks I still want to be able to
do after separating LAN into subnets, as well as maybe Print Sharing.


I don't know if this is the correct forum for a question like this and
please redirect me if you can.

I have a network operating between two houses that are about 900 Metres
apart. The setup is this:

PCs are all XP Pro.

(House1) PCs <--> Switch <--> AP (Point to Point) <--> Roof Antenna
((((( )))) (House2) Roof Antenna <--> AP (Point to Point)<--> Switch <-->
PCs and Internet(Router/Modem Combo). Currently all devices are the one LAN
(all addresses in the 192.168.0.x 255.255.255.0 subnet).

I was thinking that to keep the traffic off the APs (why? Just because and
to learn stuff) I could create two subnets at each house and place a
Router/Switch (I have two spares Vigor 2104P and Dlink DI-524) between the
switch and the AP at each house. I was also hoping to use the DLink Router
to limit the times that the kids could access the internet as they would
have to go through the router to get to the internet on the other subnet.

In order to test this theory I have setup the following at my house:

PC1 <--> Router/Switch(DLink) <--> Router/Switch(Vigor) <--> Switch <-->
PC2-3 and Internet(Router/Modem Combo).

WAN Port on DLink Router connected to LAN Port1 on Vigor Router
PC1=192.168.3.2 255.255.255.0 gateway = 192.168.3.1
DLink Router LAN = 192.168.3.1 255.255.255.0 WAN = 192.168.0.137 (I just
picked this ip randomly on the 2nd Subnet)

WAN Port on Vigor Router not yet connected
Vigor Router LAN = 192.168.0.1 255.255.255.0 WAN = not yet setup
PC2 = 192.168.0.11 255.255.255.0 Gateway=192.168.0.138
PC3 = 192.168.0.12 255.255.255.0 Gateway=192.168.0.138
Internet Router/Modem = 192.168.0.138

With this setup I can ping the 192.168.0.0 subnet from 192.168.3.0 subnet
but I can't access the internet(Can ping 192.168.0.138). I am hoping this is
because I have not yet set up the return leg of that journey(ie WAN port on
vigor to Lan port on DLink).

I have searched on the internet for a lot of information on what I am trying
to do and what I have found tends to deal with routing a private Lan onto
the internet and not really about routing between private subnets. I may
have stumbled across sites that deal with what I am trying to do but maybe
it was at a level above my current understanding.

Anyway these are some of my question/s.

Q1. Am I on the right track with these ideas?
Q2. How do I connect the two routers together? eg. WAN to WAN port with
crossover or WAN to LAN on both Routers
Q3. Should these routers do the job?
Q4. When I move to the original setup will I have to configure Access Points
on their own subnet?
Q5. Could this be done with less equipment?
Q6. I have heard the phrase 192.168.x.x addresses are private and non
routable addresses. Does this mean that they should not be routed or that
they cannot be routed or is it another meaning all together?

Thanks in advance
Troy

 

[Chuck]

Hi!

I wrote the story below before I read PChuck's article "File Sharing On A
LAN With Two Routers" and now wonder whether or not to send this message as
File Sharing and Remote Connection are two tasks I still want to be able to
do after separating LAN into subnets, as well as maybe Print Sharing.


I don't know if this is the correct forum for a question like this and
please redirect me if you can.

I have a network operating between two houses that are about 900 Metres
apart. The setup is this:

PCs are all XP Pro.

(House1) PCs <--> Switch <--> AP (Point to Point) <--> Roof Antenna
((((( )))) (House2) Roof Antenna <--> AP (Point to Point)<--> Switch <-->
PCs and Internet(Router/Modem Combo). Currently all devices are the one LAN
(all addresses in the 192.168.0.x 255.255.255.0 subnet).

I was thinking that to keep the traffic off the APs (why? Just because and
to learn stuff) I could create two subnets at each house and place a
Router/Switch (I have two spares Vigor 2104P and Dlink DI-524) between the
switch and the AP at each house. I was also hoping to use the DLink Router
to limit the times that the kids could access the internet as they would
have to go through the router to get to the internet on the other subnet.

In order to test this theory I have setup the following at my house:

PC1 <--> Router/Switch(DLink) <--> Router/Switch(Vigor) <--> Switch <-->
PC2-3 and Internet(Router/Modem Combo).

WAN Port on DLink Router connected to LAN Port1 on Vigor Router
PC1=192.168.3.2 255.255.255.0 gateway = 192.168.3.1
DLink Router LAN = 192.168.3.1 255.255.255.0 WAN = 192.168.0.137 (I just
picked this ip randomly on the 2nd Subnet)

WAN Port on Vigor Router not yet connected
Vigor Router LAN = 192.168.0.1 255.255.255.0 WAN = not yet setup
PC2 = 192.168.0.11 255.255.255.0 Gateway=192.168.0.138
PC3 = 192.168.0.12 255.255.255.0 Gateway=192.168.0.138
Internet Router/Modem = 192.168.0.138

With this setup I can ping the 192.168.0.0 subnet from 192.168.3.0 subnet
but I can't access the internet(Can ping 192.168.0.138). I am hoping this is
because I have not yet set up the return leg of that journey(ie WAN port on
vigor to Lan port on DLink).

I have searched on the internet for a lot of information on what I am trying
to do and what I have found tends to deal with routing a private Lan onto
the internet and not really about routing between private subnets. I may
have stumbled across sites that deal with what I am trying to do but maybe
it was at a level above my current understanding.

Anyway these are some of my question/s.

Q1. Am I on the right track with these ideas?
Q2. How do I connect the two routers together? eg. WAN to WAN port with
crossover or WAN to LAN on both Routers
Q3. Should these routers do the job?
Q4. When I move to the original setup will I have to configure Access Points
on their own subnet?
Q5. Could this be done with less equipment?
Q6. I have heard the phrase 192.168.x.x addresses are private and non
routable addresses. Does this mean that they should not be routed or that
they cannot be routed or is it another meaning all together?

Thanks in advance
Troy

Troy,

I see your problem, I think. On your main LAN, 192.168.0/24, the default
gateway is 192.168.0.138. On your DLink LAN, 192.168.3/24, the default gateway
is 192.168.3.1. Now, you need to define a default gateway for the DLink to use,
on its WAN connection, to connect to the Internet.

Without a default gateway assigned to the DLink WAN, any Internet traffic from
PC1 goes to its default gateway 192.168.3.1, and to the DLink WAN, and onto the
main LAN. And there it stays. The DLink WAN has to have a default gateway
defined, so the Internet traffic that it gets thru its LAN, 192.168.3.1, will go
thru 192.168.0.138. For the DLink, as for the computers on the main LAN, the
default gateway will be 192.168.0.138.

Q1 / Q2. The routers are connected properly. When you get this working, you'll
be moving all of your computers to the DLink LAN, and they will all be able to
share files. Just set the default gateway for the DLink to 192.168.0.138.
Q3. These routers should do the job.
Q4. Why do you wish to move to the original setup?
Q5. I'm not sure what you're accomplishing with the Vigor setup as a switch,
and connected to another switch. Are the Vigor and the switch located in the
same place, or are they separate?
Q6. The subnet 192.168.x.x is private (non-routable) so that it can be used on
any private (non-routed) LAN in the world, without fear of being duplicated by
any public LAN anywhere in the world. You can only use 192.168.x.x behind a NAT
router. A NAT router handles the entire 192.168.x.x subnet privately, and the
world sees only the WAN address. In your case, for instance, your main LAN sees
192.168.0.137, and that address is translated by the DLink into the 192.168.3.x
subnet.

Please let me know, at your earliest convenience, if these answers are
understandable. It would be hella easier to setup your network, then to explain
it.

 

[Troy]

Troy,

I see your problem, I think. On your main LAN, 192.168.0/24, the default
gateway is 192.168.0.138. On your DLink LAN, 192.168.3/24, the default gateway
is 192.168.3.1. Now, you need to define a default gateway for the DLink to use,
on its WAN connection, to connect to the Internet.

Without a default gateway assigned to the DLink WAN, any Internet traffic from
PC1 goes to its default gateway 192.168.3.1, and to the DLink WAN, and onto the
main LAN. And there it stays. The DLink WAN has to have a default gateway
defined, so the Internet traffic that it gets thru its LAN, 192.168.3.1, will go
thru 192.168.0.138. For the DLink, as for the computers on the main LAN, the
default gateway will be 192.168.0.138.

Q1 / Q2. The routers are connected properly. When you get this working, you'll
be moving all of your computers to the DLink LAN, and they will all be able to
share files. Just set the default gateway for the DLink to 192.168.0.138.
Q3. These routers should do the job.
Q4. Why do you wish to move to the original setup?
Q5. I'm not sure what you're accomplishing with the Vigor setup as a switch,
and connected to another switch. Are the Vigor and the switch located in the
same place, or are they separate?
Q6. The subnet 192.168.x.x is private (non-routable) so that it can be used on
any private (non-routed) LAN in the world, without fear of being duplicated by
any public LAN anywhere in the world. You can only use 192.168.x.x behind a NAT
router. A NAT router handles the entire 192.168.x.x subnet privately, and the
world sees only the WAN address. In your case, for instance, your main LAN sees
192.168.0.137, and that address is translated by the DLink into the 192.168.3.x
subnet.

Please let me know, at your earliest convenience, if these answers are
understandable. It would be hella easier to setup your network, then to explain
it.

Chuck

Thank you for your response. Just for your information some of my responses
may be 24 hours apart as I go home and try suggestions from this group. I
can't seem to find this newsgroup on my home computer for some reason.

Q1/Q2. The computers will remain as per the original setup but with Routers
placed in between the switches and APs.(Re: Q4 APs on own Subnet) Probably
remove switch at house1 though. House2 has Gigabit switch and NICs for fast
file transfers at house2. The DLink already has the Gateway set to
192.168.0.138 but with no luck accessing the internet.

Q3. OK. Thanks.

Q4. See Q1/Q2.

Q5. House2 has Gigabit switch and NICs for fast file transfers at house2.
The Switch and Router are separate in the test setup but would be together
if I get this to work properly. In the current Test setup I have the two
Routers and PC1 next to each other for ease of wiring them together.

Q6. What you have explained is basically as I remember NAT working however I
did not know that NAT would only work with the 192.168.x.x addresses. I
though it would just translate any address to and from the one WAN exposed
address. I can't say that I completely understand the term Non-Routable but
I do think I understand how NAT works and the concept of how it limits
addresses used on the WAN. Would it more accurate to say that the
192.168.x.x subnet can't be used for Public Addresses rather then to say it
can only be used for Private Addresses?

I have cabled the WAN port of the Vigor Router to a LAN Port of the DLink
Router and set the Vigor WAN ip to 192.168.3.136 255.255.255.0 and no
Gateway. I can now ping all addresses on 192.168.0.x from 192.168.3.x and
vice-versa however I still get no Ineternet access from the 192.168.3.x
subnet. Subnet 192.168.3.x PCs set with gateway 192.168.3.1 and Subnet
192.168.0.x PCs set with gateway 192.168.0.138.

Any ideas?

Regards
Troy

 

[Chuck]

Chuck

Thank you for your response. Just for your information some of my responses
may be 24 hours apart as I go home and try suggestions from this group. I
can't seem to find this newsgroup on my home computer for some reason.

Q1/Q2. The computers will remain as per the original setup but with Routers
placed in between the switches and APs.(Re: Q4 APs on own Subnet) Probably
remove switch at house1 though. House2 has Gigabit switch and NICs for fast
file transfers at house2. The DLink already has the Gateway set to
192.168.0.138 but with no luck accessing the internet.

Q3. OK. Thanks.

Q4. See Q1/Q2.

Q5. House2 has Gigabit switch and NICs for fast file transfers at house2.
The Switch and Router are separate in the test setup but would be together
if I get this to work properly. In the current Test setup I have the two
Routers and PC1 next to each other for ease of wiring them together.

Q6. What you have explained is basically as I remember NAT working however I
did not know that NAT would only work with the 192.168.x.x addresses. I
though it would just translate any address to and from the one WAN exposed
address. I can't say that I completely understand the term Non-Routable but
I do think I understand how NAT works and the concept of how it limits
addresses used on the WAN. Would it more accurate to say that the
192.168.x.x subnet can't be used for Public Addresses rather then to say it
can only be used for Private Addresses?

What's most accurate is to say that it ISN'T used for public addresses. It
COULD be used, but by agreement (RFC 1918), no network provider will setup a
routing for you. Since it isn't used publicly, it can be used privately, in
safety, by anyone.
http://www.faqs.org/rfcs/rfc1918.html

I have cabled the WAN port of the Vigor Router to a LAN Port of the DLink
Router and set the Vigor WAN ip to 192.168.3.136 255.255.255.0 and no
Gateway. I can now ping all addresses on 192.168.0.x from 192.168.3.x and
vice-versa however I still get no Ineternet access from the 192.168.3.x
subnet. Subnet 192.168.3.x PCs set with gateway 192.168.3.1 and Subnet
192.168.0.x PCs set with gateway 192.168.0.138.

Which router does PC1 connect to directly? The DLink or the Vigor? Make up
your mind please. You previously gave us:Then, which router - the DLink or the Vigor, connects to the Switch, and by its
LAN or WAN port?

 

[Troy]

What's most accurate is to say that it ISN'T used for public addresses. It
COULD be used, but by agreement (RFC 1918), no network provider will setup a
routing for you. Since it isn't used publicly, it can be used privately, in
safety, by anyone.
http://www.faqs.org/rfcs/rfc1918.html


Which router does PC1 connect to directly? The DLink or the Vigor? Make up
your mind please. You previously gave us:Then, which router - the DLink or the Vigor, connects to the Switch, and by its
LAN or WAN port?

Chuck

Sorry for the confusion.

The Setup is :

PC1 connected to DLink Router LAN Port1 (PC1 192.168.3.2/255.255.255.0 Gtwy
192.168.3.1)

DLink Router WAN Port Connected to Vigor Router LAN Port1 (DLink LAN
192.168.3.1/255.255.255.0 WAN 192.168.0.2/255.255.255.0 Gtwy 192.168.0.138)

Vigor Router WAN Port Connected to DLink Router LAN Port1 (Vigor LAN
192.168.0.1/255.255.255.0 WAN 192.168.3.136/255.255.255.0 Gtwy <Blank>)

Vigor Router LAN2 Port Connected to Gigabit Switch Port1 (DLink DGS1005D)

PC2 Connected to Gigabit Switch Port2 (PC2 192.168.0.11/255.255.255.0 Gtwy
192.168.0.138)

PC3 Connected to Gigabit Switch Port3 (PC3 192.168.0.13/255.255.255.0 Gtwy
192.168.0.138)

Speedstream 4200 Router/Modem Connected to Gigabit Switch Port4 (Speedstream
192.168.0.130/255.255.255.0)

Regards
Troy

 

[Chuck]

Chuck

Sorry for the confusion.

The Setup is :

PC1 connected to DLink Router LAN Port1 (PC1 192.168.3.2/255.255.255.0 Gtwy
192.168.3.1)

DLink Router WAN Port Connected to Vigor Router LAN Port1 (DLink LAN
192.168.3.1/255.255.255.0 WAN 192.168.0.2/255.255.255.0 Gtwy 192.168.0.138)

Vigor Router WAN Port Connected to DLink Router LAN Port1 (Vigor LAN
192.168.0.1/255.255.255.0 WAN 192.168.3.136/255.255.255.0 Gtwy <Blank>)

Vigor Router LAN2 Port Connected to Gigabit Switch Port1 (DLink DGS1005D)

PC2 Connected to Gigabit Switch Port2 (PC2 192.168.0.11/255.255.255.0 Gtwy
192.168.0.138)

PC3 Connected to Gigabit Switch Port3 (PC3 192.168.0.13/255.255.255.0 Gtwy
192.168.0.138)

Speedstream 4200 Router/Modem Connected to Gigabit Switch Port4 (Speedstream
192.168.0.130/255.255.255.0)

Regards
Troy

Troy,

Try taking the Vigor out of the picture. Connect the DLink WAN to the DLink
DGS1005D.

Where is 192.168.0.138? Should that be 192.168.0.130?

 

[Troy]

Troy,

Try taking the Vigor out of the picture. Connect the DLink WAN to the DLink
DGS1005D.

Where is 192.168.0.138? Should that be 192.168.0.130?

Chuck

Sorry, you are correct 192.168.0.130 should have been 192.168.0.138. It is
the Speedstream 4200 Modem/Router that gives internet access.

I think I did already try the setup without the vigor Router and still could
not access the internet from the 192.168.3.x subnet. I will confirm that is
the case over the weekend.

Thank you for your help so far.

Regards
Troy

 

[Chuck]

Chuck

Sorry, you are correct 192.168.0.130 should have been 192.168.0.138. It is
the Speedstream 4200 Modem/Router that gives internet access.

I think I did already try the setup without the vigor Router and still could
not access the internet from the 192.168.3.x subnet. I will confirm that is
the case over the weekend.

Thank you for your help so far.

Regards
Troy

OK, Troy. We'll take it one step at a time. Let us know what you find out, and
I'll look thru your analysis again a few times while I wait.

 

[Troy]

OK, Troy. We'll take it one step at a time. Let us know what you find out, and
I'll look thru your analysis again a few times while I wait.

Chuck

I removed the Vigor Router from the equation and verified the connection of
the WAN port on the DLink Router to the DLink Switch Port 1.

WAN settings for the DLink Router are still the same at IP =
192.168.0.2/255.255.255.0 Gtwy = 192.168.0.138) Prmy DNS = 192.168.0.138
Secondary DNS = 0.0.0.0.

Can Ping 192.168.0.x subnet.

Still cannot access the Internet with IE (web page doesn't display) however
when i tracert to 66.102.7.104 (www.google.com) I get 20 hops to the
destination OK.

Regards

Troy

 

[Chuck]

Chuck

I removed the Vigor Router from the equation and verified the connection of
the WAN port on the DLink Router to the DLink Switch Port 1.

WAN settings for the DLink Router are still the same at IP =
192.168.0.2/255.255.255.0 Gtwy = 192.168.0.138) Prmy DNS = 192.168.0.138
Secondary DNS = 0.0.0.0.

Can Ping 192.168.0.x subnet.

Still cannot access the Internet with IE (web page doesn't display) however
when i tracert to 66.102.7.104 (www.google.com) I get 20 hops to the
destination OK.

Regards

Troy

Try,

What happens if you try http://66.102.7.104 from PC1 and PC2?

Also, let's look at "ipconfig /all" from PC1 and PC2.

 

[Troy]

Try,

What happens if you try http://66.102.7.104 from PC1 and PC2?

Also, let's look at "ipconfig /all" from PC1 and PC2.

Chuck

I tried using the ip address 66.102.7.104 in the address bar in IE and it
worked. I forgot to try it on PC2 and PC3 but these PCs don't have problems
connecting to the internet. I will however do this tonight and let you know.

Please find below ipconfig /all dump for PC1 and PC2:

PC1
Windows IP Configuration

Host Name . . . . . . . . . . . . : p432

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet
Adapter

Physical Address. . . . . . . . . : 00-13-D3-38-2A-AC

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.3.2

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.3.1

Ethernet adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected

Description . . . . . . . . . . . : Belkin 802.11g Wireless Card

Physical Address. . . . . . . . . : 00-11-50-62-E9-8F


PC2
Windows IP Configuration

Host Name . . . . . . . . . . . . : p420

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : BigPond

Ethernet adapter Local Area Connection 4:

Connection-specific DNS Suffix . : BigPond

Description . . . . . . . . . . . : D-Link DGE-530T Gigabit Ethernet
Adapter #2

Physical Address. . . . . . . . . : 00-11-95-DE-C6-D8

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.13

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.138

DHCP Server . . . . . . . . . . . : 192.168.0.138

DNS Servers . . . . . . . . . . . : 192.168.0.138

Lease Obtained. . . . . . . . . . : Tuesday, 7 March 2006 5:54:55 PM

Lease Expires . . . . . . . . . . : Tuesday, 19 January 2038 1:14:07
PM


Regards

Troy

 

[Chuck]

I tried using the ip address 66.102.7.104 in the address bar in IE and it
worked. I forgot to try it on PC2 and PC3 but these PCs don't have problems
connecting to the internet. I will however do this tonight and let you know.

Please find below ipconfig /all dump for PC1 and PC2:

PC1
Windows IP Configuration

Host Name . . . . . . . . . . . . : p432

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet
Adapter

Physical Address. . . . . . . . . : 00-13-D3-38-2A-AC

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.3.2

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.3.1

Ethernet adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected

Description . . . . . . . . . . . : Belkin 802.11g Wireless Card

Physical Address. . . . . . . . . : 00-11-50-62-E9-8F


PC2
Windows IP Configuration

Host Name . . . . . . . . . . . . : p420

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : BigPond

Ethernet adapter Local Area Connection 4:

Connection-specific DNS Suffix . : BigPond

Description . . . . . . . . . . . : D-Link DGE-530T Gigabit Ethernet
Adapter #2

Physical Address. . . . . . . . . : 00-11-95-DE-C6-D8

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.13

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.138

DHCP Server . . . . . . . . . . . : 192.168.0.138

DNS Servers . . . . . . . . . . . : 192.168.0.138

Lease Obtained. . . . . . . . . . : Tuesday, 7 March 2006 5:54:55 PM

Lease Expires . . . . . . . . . . : Tuesday, 19 January 2038 1:14:07
PM


Regards

Troy

Troy,

If you can access 66.102.7.104, but not www.google.com, you have a DNS problem.
Looking at ipconfig for PC1, I don't see any DNS servers listed. That's a
problem. PC2 is using 192.168.0.138 as a DNS server - try setting PC1 up with
that.
<http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html#BasicSettings>
http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html#BasicSettings

 

[Troy]

Troy,

If you can access 66.102.7.104, but not www.google.com, you have a DNS problem.
Looking at ipconfig for PC1, I don't see any DNS servers listed. That's a
problem. PC2 is using 192.168.0.138 as a DNS server - try setting PC1 up with
<http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html#
BasicSettings>http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html#B
asicSettings

Chuck

Should the PC DNS configuration handle this or should the Router DNS
configuration handle it?

For ease of configuration and centralisation would this not be better done
in the Router if that is it's purpose or am I completely off track here?

As the Router is currently setup with a Primary DNS of 192.168.0.138 should
I set the DNS on the NIC of PC1 to 192.168.0.138 (Modem/Router on
192.168.0.x subnet) or to 192.168.3.1 (Router on 192.168.3.x subnet which
subsequently points to 192.168.0.138)?

Will give both configurations a try tonight and let you know.

Thanks for your help so far.

Regards

Troy

 

[Troy]

5:54:55 up
<http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html#
http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html#B


Chuck

Should the PC DNS configuration handle this or should the Router DNS
configuration handle it?

For ease of configuration and centralisation would this not be better done
in the Router if that is it's purpose or am I completely off track here?

As the Router is currently setup with a Primary DNS of 192.168.0.138 should
I set the DNS on the NIC of PC1 to 192.168.0.138 (Modem/Router on
192.168.0.x subnet) or to 192.168.3.1 (Router on 192.168.3.x subnet which
subsequently points to 192.168.0.138)?

Will give both configurations a try tonight and let you know.

Thanks for your help so far.

Regards

Troy

Chuck

Changed the DNS IP on the NIC on PC1 to 192.168.0.138 and the Internet
sprang to life. Tried changing the DNS IP to 192.168.3.1 but this did NOT
work. I guess for me this raises the question what is the DNS Address for on
the Router or is it just not used in my situation.

Anyhow this seems to have solved the issues/questions that I have had and I
wish to thank you for your assistance.

I think I will have some more questions about file sharing and Remoting
between subnets but I think I need to let this stuff soak in and do some
more reading about subnets.

Thanks again.

Troy

 

[Chuck]

Chuck

Changed the DNS IP on the NIC on PC1 to 192.168.0.138 and the Internet
sprang to life. Tried changing the DNS IP to 192.168.3.1 but this did NOT
work. I guess for me this raises the question what is the DNS Address for on
the Router or is it just not used in my situation.

Anyhow this seems to have solved the issues/questions that I have had and I
wish to thank you for your assistance.

I think I will have some more questions about file sharing and Remoting
between subnets but I think I need to let this stuff soak in and do some
more reading about subnets.

Thanks again.

Troy

Troy,

That's great news! Some NAT routers will act as DNS relays (and talk to your
ISPs DNS server transparently); with others you have to set each computer with
the IP address of your ISP's DNS servers, and each computer talks directly to
that server.

Apparently, your router at 192.168.0.138 WILL act as a DNS relay, but your
router at 192.168.3.1 won't.

I think we both learned a bit here. Ask more questions whenever this stuff has
soaked in.