Rookie stranded for days

I am a network rookie, and have been stuck for days. Would greatly
appreciate assistance in getting unstuck or at least pointed in the
right direction. Everything works fine for a while but eventually I
lose the ability to connect to the internet from one (and only one)
computer. Here's a visual of my network setup/configuration:


Internet (static ip)
|
|
+--------+ 192.168.1.1
| Router |--------------+-----------------+-----------------+
+--------+ | | |
|192.168.1.100 |192.168.1.2 |
192.168.1.3
+--------+ +--------+ +--------+
| Win 03 | | Win 03 | | Win 03 |
| Server | | Server | | Server |
| Std x64| | Web Ed.| | Web Ed.|
+--------+ +--------+ +--------+
|172.16.1.1 |172.16.1.2 |
172.16.1.3
| | |
| +--------+ |
+-------------| Switch |------------+
+--------+


Each server has two Nic cards. The router is a standard Actiontec
MI424WR received with my Fios service. The switch is a D-Link Giabit
(DGS-2205). Sql Server is running on the Win Server Std. The other
two machines are worker bees and only run server so they'll have
access to a TCPIP stack that hasn't been handicapped; their primarily
is to retrieve intellegence from the web and make updates to the
database (on the Std Sever).

The intent of adding the switch was several fold: 1) get database
traffic off the router and 2) limit SQL Server access to only the
internal network. Everything works fine for a while. However, some
period of time after beginning database updates (e.g. 172.16.1.2 ->
172.16.1.1) the Std Server loses it's ability to connect to the
internet (via web browser or .Net). When this occurs external
addresses (i.e. on the Internet) can still be found via ping and
tracert from the Std Server and access on the worker bees is fine/
unimpeded. It's only the Std Server that's affected. I've found
nothing to resolve the issue short of rebooting the Router or
rebooting the Std Server (and doing either seems to resolve the
issue). Strange, no?

Here's some more background:
The Std Server is running SP2 and is not a domain controller or
running DNS (DNS was configured at one point). There is only a single
gateway configured (192.168.1.1) which is on the Nic's connected to
192.168.0.0 network. The Nic's for the 172.16.0.0 network are
configured without a gateway, defined with static routes (are these
correct?), have all protocols except TCPIP disabled (e.g. MS Network)
and "Register this connection's addresses in DNS" is unchecked.


IPCONFIG /all and route PRINT are included below:

IPCONFIG /all:
-------------
Windows IP Configuration

Host Name . . . . . . . . . . . . : leed
Primary Dns Suffix . . . . . . . : 140.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : 140.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet
Physical Address. . . . . . . . . : 00-13-72-3D-88-8A
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1

Ethernet adapter Local Area Connection 4:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8169/8110 Family
Gigabit Ether
net NIC #3
Physical Address. . . . . . . . . : 00-18-E7-09-19-F9
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.16.1.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :


route PRINT:
-----------

IPv4 Route Table
================================================== =========================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 13 72 3d 88 8a ...... Broadcom NetXtreme Gigabit
Ethernet
0x10004 ...00 18 e7 09 19 f9 ...... Realtek RTL8169/8110 Family
Gigabit Ethernet
NIC #3
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.1.1
192.168.1.100 20
127.0.0.0 255.0.0.0 127.0.0.1
127.0.0.1 1
172.16.1.0 255.255.255.0 172.16.1.1
172.16.1.1 2
172.16.1.1 255.255.255.255 127.0.0.1
127.0.0.1 2
172.16.1.2 255.255.255.255 172.16.1.1
172.16.1.1 1
172.16.1.3 255.255.255.255 172.16.1.1
172.16.1.1 1
172.16.255.255 255.255.255.255 172.16.1.1
172.16.1.1 2
192.168.1.0 255.255.255.0 192.168.1.100
192.168.1.100 20
192.168.1.100 255.255.255.255 127.0.0.1
127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.100
192.168.1.100 20
224.0.0.0 240.0.0.0 172.16.1.1
172.16.1.1 2
224.0.0.0 240.0.0.0 192.168.1.100
192.168.1.100 20
255.255.255.255 255.255.255.255 172.16.1.1
172.16.1.1 1
255.255.255.255 255.255.255.255 192.168.1.100
192.168.1.100 1
Default Gateway: 192.168.1.1
================================================== =========================
Persistent Routes:
Network Address Netmask Gateway Address Metric
172.16.1.2 255.255.255.255 172.16.1.1 1
172.16.1.3 255.255.255.255 172.16.1.1 1

-------- END ---------

Is your router works as a DNS server??I think you are failing here:

DNS Servers . . . . . . . . . . . : 192.168.1.1


Ashish

"(E-Mail Removed)" wrote:

> I am a network rookie, and have been stuck for days. Would greatly
> appreciate assistance in getting unstuck or at least pointed in the
> right direction. Everything works fine for a while but eventually I
> lose the ability to connect to the internet from one (and only one)
> computer. Here's a visual of my network setup/configuration:
>
>
> Internet (static ip)
> |
> |
> +--------+ 192.168.1.1
> | Router |--------------+-----------------+-----------------+
> +--------+ | | |
> |192.168.1.100 |192.168.1.2 |
> 192.168.1.3
> +--------+ +--------+ +--------+
> | Win 03 | | Win 03 | | Win 03 |
> | Server | | Server | | Server |
> | Std x64| | Web Ed.| | Web Ed.|
> +--------+ +--------+ +--------+
> |172.16.1.1 |172.16.1.2 |
> 172.16.1.3
> | | |
> | +--------+ |
> +-------------| Switch |------------+
> +--------+
>
>
> Each server has two Nic cards. The router is a standard Actiontec
> MI424WR received with my Fios service. The switch is a D-Link Giabit
> (DGS-2205). Sql Server is running on the Win Server Std. The other
> two machines are worker bees and only run server so they'll have
> access to a TCPIP stack that hasn't been handicapped; their primarily
> is to retrieve intellegence from the web and make updates to the
> database (on the Std Sever).
>
> The intent of adding the switch was several fold: 1) get database
> traffic off the router and 2) limit SQL Server access to only the
> internal network. Everything works fine for a while. However, some
> period of time after beginning database updates (e.g. 172.16.1.2 ->
> 172.16.1.1) the Std Server loses it's ability to connect to the
> internet (via web browser or .Net). When this occurs external
> addresses (i.e. on the Internet) can still be found via ping and
> tracert from the Std Server and access on the worker bees is fine/
> unimpeded. It's only the Std Server that's affected. I've found
> nothing to resolve the issue short of rebooting the Router or
> rebooting the Std Server (and doing either seems to resolve the
> issue). Strange, no?
>
> Here's some more background:
> The Std Server is running SP2 and is not a domain controller or
> running DNS (DNS was configured at one point). There is only a single
> gateway configured (192.168.1.1) which is on the Nic's connected to
> 192.168.0.0 network. The Nic's for the 172.16.0.0 network are
> configured without a gateway, defined with static routes (are these
> correct?), have all protocols except TCPIP disabled (e.g. MS Network)
> and "Register this connection's addresses in DNS" is unchecked.
>
>
> IPCONFIG /all and route PRINT are included below:
>
> IPCONFIG /all:
> -------------
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : leed
> Primary Dns Suffix . . . . . . . : 140.com
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : 140.com
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
> Ethernet
> Physical Address. . . . . . . . . : 00-13-72-3D-88-8A
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.100
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 192.168.1.1
>
> Ethernet adapter Local Area Connection 4:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Realtek RTL8169/8110 Family
> Gigabit Ether
> net NIC #3
> Physical Address. . . . . . . . . : 00-18-E7-09-19-F9
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 172.16.1.1
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . :
>
>
> route PRINT:
> -----------
>
> IPv4 Route Table
> ================================================== =========================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x10003 ...00 13 72 3d 88 8a ...... Broadcom NetXtreme Gigabit
> Ethernet
> 0x10004 ...00 18 e7 09 19 f9 ...... Realtek RTL8169/8110 Family
> Gigabit Ethernet
> NIC #3
> ================================================== =========================
> ================================================== =========================
> Active Routes:
> Network Destination Netmask Gateway Interface
> Metric
> 0.0.0.0 0.0.0.0 192.168.1.1
> 192.168.1.100 20
> 127.0.0.0 255.0.0.0 127.0.0.1
> 127.0.0.1 1
> 172.16.1.0 255.255.255.0 172.16.1.1
> 172.16.1.1 2
> 172.16.1.1 255.255.255.255 127.0.0.1
> 127.0.0.1 2
> 172.16.1.2 255.255.255.255 172.16.1.1
> 172.16.1.1 1
> 172.16.1.3 255.255.255.255 172.16.1.1
> 172.16.1.1 1
> 172.16.255.255 255.255.255.255 172.16.1.1
> 172.16.1.1 2
> 192.168.1.0 255.255.255.0 192.168.1.100
> 192.168.1.100 20
> 192.168.1.100 255.255.255.255 127.0.0.1
> 127.0.0.1 20
> 192.168.1.255 255.255.255.255 192.168.1.100
> 192.168.1.100 20
> 224.0.0.0 240.0.0.0 172.16.1.1
> 172.16.1.1 2
> 224.0.0.0 240.0.0.0 192.168.1.100
> 192.168.1.100 20
> 255.255.255.255 255.255.255.255 172.16.1.1
> 172.16.1.1 1
> 255.255.255.255 255.255.255.255 192.168.1.100
> 192.168.1.100 1
> Default Gateway: 192.168.1.1
> ================================================== =========================
> Persistent Routes:
> Network Address Netmask Gateway Address Metric
> 172.16.1.2 255.255.255.255 172.16.1.1 1
> 172.16.1.3 255.255.255.255 172.16.1.1 1
>
> -------- END ---------
>
>

(E-Mail Removed) wrote:
> I am a network rookie, and have been stuck for days. Would greatly
> appreciate assistance in getting unstuck or at least pointed in the
> right direction. Everything works fine for a while but eventually I
> lose the ability to connect to the internet from one (and only one)
> computer. Here's a visual of my network setup/configuration:
>
>
> Internet (static ip)
> |
> |
> +--------+ 192.168.1.1
> | Router |--------------+-----------------+-----------------+
> +--------+ | | |
> |192.168.1.100 |192.168.1.2 |
> 192.168.1.3
> +--------+ +--------+ +--------+
> | Win 03 | | Win 03 | | Win 03 |
> | Server | | Server | | Server |
> | Std x64| | Web Ed.| | Web Ed.|
> +--------+ +--------+ +--------+
> |172.16.1.1 |172.16.1.2 |
> 172.16.1.3
> | | |
> | +--------+ |
> +-------------| Switch |------------+
> +--------+
>
>
> Each server has two Nic cards. The router is a standard Actiontec
> MI424WR received with my Fios service. The switch is a D-Link Giabit
> (DGS-2205). Sql Server is running on the Win Server Std. The other
> two machines are worker bees and only run server so they'll have
> access to a TCPIP stack that hasn't been handicapped; their primarily
> is to retrieve intellegence from the web and make updates to the
> database (on the Std Sever).
>
> The intent of adding the switch was several fold: 1) get database
> traffic off the router and 2) limit SQL Server access to only the
> internal network. Everything works fine for a while. However, some
> period of time after beginning database updates (e.g. 172.16.1.2 ->
> 172.16.1.1) the Std Server loses it's ability to connect to the
> internet (via web browser or .Net). When this occurs external
> addresses (i.e. on the Internet) can still be found via ping and
> tracert from the Std Server and access on the worker bees is fine/
> unimpeded. It's only the Std Server that's affected. I've found
> nothing to resolve the issue short of rebooting the Router or
> rebooting the Std Server (and doing either seems to resolve the
> issue). Strange, no?
>
> Here's some more background:
> The Std Server is running SP2 and is not a domain controller or
> running DNS (DNS was configured at one point). There is only a single
> gateway configured (192.168.1.1) which is on the Nic's connected to
> 192.168.0.0 network. The Nic's for the 172.16.0.0 network are
> configured without a gateway, defined with static routes (are these
> correct?), have all protocols except TCPIP disabled (e.g. MS Network)
> and "Register this connection's addresses in DNS" is unchecked.
>
>
> IPCONFIG /all and route PRINT are included below:
>
> IPCONFIG /all:
> -------------
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : leed
> Primary Dns Suffix . . . . . . . : 140.com
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : 140.com
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
> Ethernet
> Physical Address. . . . . . . . . : 00-13-72-3D-88-8A
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.100
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 192.168.1.1
>
> Ethernet adapter Local Area Connection 4:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Realtek RTL8169/8110 Family
> Gigabit Ether
> net NIC #3
> Physical Address. . . . . . . . . : 00-18-E7-09-19-F9
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 172.16.1.1
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . :
>
>
> route PRINT:
> -----------
>
> IPv4 Route Table
> ================================================== =========================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x10003 ...00 13 72 3d 88 8a ...... Broadcom NetXtreme Gigabit
> Ethernet
> 0x10004 ...00 18 e7 09 19 f9 ...... Realtek RTL8169/8110 Family
> Gigabit Ethernet
> NIC #3
> ================================================== =========================
> ================================================== =========================
> Active Routes:
> Network Destination Netmask Gateway Interface
> Metric
> 0.0.0.0 0.0.0.0 192.168.1.1
> 192.168.1.100 20
> 127.0.0.0 255.0.0.0 127.0.0.1
> 127.0.0.1 1
> 172.16.1.0 255.255.255.0 172.16.1.1
> 172.16.1.1 2
> 172.16.1.1 255.255.255.255 127.0.0.1
> 127.0.0.1 2
> 172.16.1.2 255.255.255.255 172.16.1.1
> 172.16.1.1 1
> 172.16.1.3 255.255.255.255 172.16.1.1
> 172.16.1.1 1
> 172.16.255.255 255.255.255.255 172.16.1.1
> 172.16.1.1 2
> 192.168.1.0 255.255.255.0 192.168.1.100
> 192.168.1.100 20
> 192.168.1.100 255.255.255.255 127.0.0.1
> 127.0.0.1 20
> 192.168.1.255 255.255.255.255 192.168.1.100
> 192.168.1.100 20
> 224.0.0.0 240.0.0.0 172.16.1.1
> 172.16.1.1 2
> 224.0.0.0 240.0.0.0 192.168.1.100
> 192.168.1.100 20
> 255.255.255.255 255.255.255.255 172.16.1.1
> 172.16.1.1 1
> 255.255.255.255 255.255.255.255 192.168.1.100
> 192.168.1.100 1
> Default Gateway: 192.168.1.1
> ================================================== =========================
> Persistent Routes:
> Network Address Netmask Gateway Address Metric
> 172.16.1.2 255.255.255.255 172.16.1.1 1
> 172.16.1.3 255.255.255.255 172.16.1.1 1
>
> -------- END ---------
>

I'm guessing it all worked fine before you decided to "move database
traffic off the router"?

Put it back the way it was. There are some fundamental flaws in your
network design.

1) Traffic going from server to server doesn't touch your router.
Traffic will only hit the router if it's destined for the Internet.

2) Everything behind the router is considered the "internal network"
The 192.168.x.x network is not publicly addressable, cannot be reached
from the Internet and therefore is internal only.

3) It looks like you've created static routes on one of those servers.
That is also unnecessary and could be where the issue lies. Static
routes are needed only when traversing a router. Since there is no
router between the local servers, static routes are not necessary.

Your network topology should look like this:

--------+ +-----------+
Router |-----------| Switch |
--------+ +-----------+
|
|
----------+-----------
| | |
| | |
| | |
+--------+ +--------+ +--------+
| Win 03 | | Win 03 | | Win 03 |
| Server | | Server | | Server |
| Std x64| | Web Ed.| | Web Ed.|
+--------+ +--------+ +--------+


Just do something simpler like that and I will bet that your network
issues disappear.

James Beukelman wrote:
> (E-Mail Removed) wrote:
>> I am a network rookie, and have been stuck for days. Would greatly
>> appreciate assistance in getting unstuck or at least pointed in the
>> right direction. Everything works fine for a while but eventually I
>> lose the ability to connect to the internet from one (and only one)
>> computer. Here's a visual of my network setup/configuration:
>>
>>
>> Internet (static ip)
>> |
>> |
>> +--------+ 192.168.1.1
>> | Router |--------------+-----------------+-----------------+
>> +--------+ | | |
>> |192.168.1.100 |192.168.1.2 |
>> 192.168.1.3
>> +--------+ +--------+ +--------+
>> | Win 03 | | Win 03 | | Win 03 |
>> | Server | | Server | | Server |
>> | Std x64| | Web Ed.| | Web Ed.|
>> +--------+ +--------+ +--------+
>> |172.16.1.1 |172.16.1.2 |
>> 172.16.1.3
>> | | |
>> | +--------+ |
>> +-------------| Switch |------------+
>> +--------+
>>
>>
>> Each server has two Nic cards. The router is a standard Actiontec
>> MI424WR received with my Fios service. The switch is a D-Link Giabit
>> (DGS-2205). Sql Server is running on the Win Server Std. The other
>> two machines are worker bees and only run server so they'll have
>> access to a TCPIP stack that hasn't been handicapped; their primarily
>> is to retrieve intellegence from the web and make updates to the
>> database (on the Std Sever).
>>
>> The intent of adding the switch was several fold: 1) get database
>> traffic off the router and 2) limit SQL Server access to only the
>> internal network. Everything works fine for a while. However, some
>> period of time after beginning database updates (e.g. 172.16.1.2 ->
>> 172.16.1.1) the Std Server loses it's ability to connect to the
>> internet (via web browser or .Net). When this occurs external
>> addresses (i.e. on the Internet) can still be found via ping and
>> tracert from the Std Server and access on the worker bees is fine/
>> unimpeded. It's only the Std Server that's affected. I've found
>> nothing to resolve the issue short of rebooting the Router or
>> rebooting the Std Server (and doing either seems to resolve the
>> issue). Strange, no?
>>
>> Here's some more background:
>> The Std Server is running SP2 and is not a domain controller or
>> running DNS (DNS was configured at one point). There is only a single
>> gateway configured (192.168.1.1) which is on the Nic's connected to
>> 192.168.0.0 network. The Nic's for the 172.16.0.0 network are
>> configured without a gateway, defined with static routes (are these
>> correct?), have all protocols except TCPIP disabled (e.g. MS Network)
>> and "Register this connection's addresses in DNS" is unchecked.
>>
>>
>> IPCONFIG /all and route PRINT are included below:
>>
>> IPCONFIG /all:
>> -------------
>> Windows IP Configuration
>>
>> Host Name . . . . . . . . . . . . : leed
>> Primary Dns Suffix . . . . . . . : 140.com
>> Node Type . . . . . . . . . . . . : Unknown
>> IP Routing Enabled. . . . . . . . : No
>> WINS Proxy Enabled. . . . . . . . : No
>> DNS Suffix Search List. . . . . . : 140.com
>>
>> Ethernet adapter Local Area Connection:
>>
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
>> Ethernet
>> Physical Address. . . . . . . . . : 00-13-72-3D-88-8A
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 192.168.1.100
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.1.1
>> DNS Servers . . . . . . . . . . . : 192.168.1.1
>>
>> Ethernet adapter Local Area Connection 4:
>>
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : Realtek RTL8169/8110 Family
>> Gigabit Ether
>> net NIC #3
>> Physical Address. . . . . . . . . : 00-18-E7-09-19-F9
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 172.16.1.1
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . :
>>
>>
>> route PRINT:
>> -----------
>>
>> IPv4 Route Table
>> ================================================== =========================
>>
>> Interface List
>> 0x1 ........................... MS TCP Loopback interface
>> 0x10003 ...00 13 72 3d 88 8a ...... Broadcom NetXtreme Gigabit
>> Ethernet
>> 0x10004 ...00 18 e7 09 19 f9 ...... Realtek RTL8169/8110 Family
>> Gigabit Ethernet
>> NIC #3
>> ================================================== =========================
>>
>> ================================================== =========================
>>
>> Active Routes:
>> Network Destination Netmask Gateway Interface
>> Metric
>> 0.0.0.0 0.0.0.0 192.168.1.1
>> 192.168.1.100 20
>> 127.0.0.0 255.0.0.0 127.0.0.1
>> 127.0.0.1 1
>> 172.16.1.0 255.255.255.0 172.16.1.1
>> 172.16.1.1 2
>> 172.16.1.1 255.255.255.255 127.0.0.1
>> 127.0.0.1 2
>> 172.16.1.2 255.255.255.255 172.16.1.1
>> 172.16.1.1 1
>> 172.16.1.3 255.255.255.255 172.16.1.1
>> 172.16.1.1 1
>> 172.16.255.255 255.255.255.255 172.16.1.1
>> 172.16.1.1 2
>> 192.168.1.0 255.255.255.0 192.168.1.100
>> 192.168.1.100 20
>> 192.168.1.100 255.255.255.255 127.0.0.1
>> 127.0.0.1 20
>> 192.168.1.255 255.255.255.255 192.168.1.100
>> 192.168.1.100 20
>> 224.0.0.0 240.0.0.0 172.16.1.1
>> 172.16.1.1 2
>> 224.0.0.0 240.0.0.0 192.168.1.100
>> 192.168.1.100 20
>> 255.255.255.255 255.255.255.255 172.16.1.1
>> 172.16.1.1 1
>> 255.255.255.255 255.255.255.255 192.168.1.100
>> 192.168.1.100 1
>> Default Gateway: 192.168.1.1
>> ================================================== =========================
>>
>> Persistent Routes:
>> Network Address Netmask Gateway Address Metric
>> 172.16.1.2 255.255.255.255 172.16.1.1 1
>> 172.16.1.3 255.255.255.255 172.16.1.1 1
>>
>> -------- END ---------
>>
>
> I'm guessing it all worked fine before you decided to "move database
> traffic off the router"?
>
> Put it back the way it was. There are some fundamental flaws in your
> network design.
>
> 1) Traffic going from server to server doesn't touch your router.
> Traffic will only hit the router if it's destined for the Internet.
>
> 2) Everything behind the router is considered the "internal network"
> The 192.168.x.x network is not publicly addressable, cannot be reached
> from the Internet and therefore is internal only.
>
> 3) It looks like you've created static routes on one of those servers.
> That is also unnecessary and could be where the issue lies. Static
> routes are needed only when traversing a router. Since there is no
> router between the local servers, static routes are not necessary.
>
> Your network topology should look like this:
>
> --------+ +-----------+
> Router |-----------| Switch |
> --------+ +-----------+
> |
> |
> ----------+-----------
> | | |
> | | |
> | | |
> +--------+ +--------+ +--------+
> | Win 03 | | Win 03 | | Win 03 |
> | Server | | Server | | Server |
> | Std x64| | Web Ed.| | Web Ed.|
> +--------+ +--------+ +--------+
>
>
> Just do something simpler like that and I will bet that your network
> issues disappear.

Actually on second thought, I take back what I said about only needing
static routes to traverse a router. But if you redesign the network the
way I showed you, you won't need static routes, and you'll have a much
simpler and less problematic network.

--cheers

James: Don't know why you took it back, 'cause effectively, you were
right the first time.

rlw:

You don't need a static route to reach a network to which you're
directly connected. So if you have a NIC in the 172.16.1.0 network, it
serves no purpose to have a route to that network configured.

You also have some screwy things going on in your routing table - like
routing 127.0.0.1 to 172.16.1.2 at one point?!

James is right, though, about the design. Especially since, with no
metrics or hard-coded IP addresses in your application code to tell them
otherwise, there's no way for you to guarantee which path the traffic
will take between the machines anyway.

Keep it simple.

grep


James Beukelman wrote:
> James Beukelman wrote:
>
>> (E-Mail Removed) wrote:
>>
>>> I am a network rookie, and have been stuck for days. Would greatly
>>> appreciate assistance in getting unstuck or at least pointed in the
>>> right direction. Everything works fine for a while but eventually I
>>> lose the ability to connect to the internet from one (and only one)
>>> computer. Here's a visual of my network setup/configuration:
>>>
>>>
>>> Internet (static ip)
>>> |
>>> |
>>> +--------+ 192.168.1.1
>>> | Router |--------------+-----------------+-----------------+
>>> +--------+ | | |
>>> |192.168.1.100 |192.168.1.2 |
>>> 192.168.1.3
>>> +--------+ +--------+ +--------+
>>> | Win 03 | | Win 03 | | Win 03 |
>>> | Server | | Server | | Server |
>>> | Std x64| | Web Ed.| | Web Ed.|
>>> +--------+ +--------+ +--------+
>>> |172.16.1.1 |172.16.1.2 |
>>> 172.16.1.3
>>> | | |
>>> | +--------+ |
>>> +-------------| Switch |------------+
>>> +--------+
>>>
>>>
>>> Each server has two Nic cards. The router is a standard Actiontec
>>> MI424WR received with my Fios service. The switch is a D-Link Giabit
>>> (DGS-2205). Sql Server is running on the Win Server Std. The other
>>> two machines are worker bees and only run server so they'll have
>>> access to a TCPIP stack that hasn't been handicapped; their primarily
>>> is to retrieve intellegence from the web and make updates to the
>>> database (on the Std Sever).
>>>
>>> The intent of adding the switch was several fold: 1) get database
>>> traffic off the router and 2) limit SQL Server access to only the
>>> internal network. Everything works fine for a while. However, some
>>> period of time after beginning database updates (e.g. 172.16.1.2 ->
>>> 172.16.1.1) the Std Server loses it's ability to connect to the
>>> internet (via web browser or .Net). When this occurs external
>>> addresses (i.e. on the Internet) can still be found via ping and
>>> tracert from the Std Server and access on the worker bees is fine/
>>> unimpeded. It's only the Std Server that's affected. I've found
>>> nothing to resolve the issue short of rebooting the Router or
>>> rebooting the Std Server (and doing either seems to resolve the
>>> issue). Strange, no?
>>>
>>> Here's some more background:
>>> The Std Server is running SP2 and is not a domain controller or
>>> running DNS (DNS was configured at one point). There is only a single
>>> gateway configured (192.168.1.1) which is on the Nic's connected to
>>> 192.168.0.0 network. The Nic's for the 172.16.0.0 network are
>>> configured without a gateway, defined with static routes (are these
>>> correct?), have all protocols except TCPIP disabled (e.g. MS Network)
>>> and "Register this connection's addresses in DNS" is unchecked.
>>>
>>>
>>> IPCONFIG /all and route PRINT are included below:
>>>
>>> IPCONFIG /all:
>>> -------------
>>> Windows IP Configuration
>>>
>>> Host Name . . . . . . . . . . . . : leed
>>> Primary Dns Suffix . . . . . . . : 140.com
>>> Node Type . . . . . . . . . . . . : Unknown
>>> IP Routing Enabled. . . . . . . . : No
>>> WINS Proxy Enabled. . . . . . . . : No
>>> DNS Suffix Search List. . . . . . : 140.com
>>>
>>> Ethernet adapter Local Area Connection:
>>>
>>> Connection-specific DNS Suffix . :
>>> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
>>> Ethernet
>>> Physical Address. . . . . . . . . : 00-13-72-3D-88-8A
>>> DHCP Enabled. . . . . . . . . . . : No
>>> IP Address. . . . . . . . . . . . : 192.168.1.100
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>> DNS Servers . . . . . . . . . . . : 192.168.1.1
>>>
>>> Ethernet adapter Local Area Connection 4:
>>>
>>> Connection-specific DNS Suffix . :
>>> Description . . . . . . . . . . . : Realtek RTL8169/8110 Family
>>> Gigabit Ether
>>> net NIC #3
>>> Physical Address. . . . . . . . . : 00-18-E7-09-19-F9
>>> DHCP Enabled. . . . . . . . . . . : No
>>> IP Address. . . . . . . . . . . . : 172.16.1.1
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . :
>>>
>>>
>>> route PRINT:
>>> -----------
>>>
>>> IPv4 Route Table
>>> ================================================== =========================
>>>
>>> Interface List
>>> 0x1 ........................... MS TCP Loopback interface
>>> 0x10003 ...00 13 72 3d 88 8a ...... Broadcom NetXtreme Gigabit
>>> Ethernet
>>> 0x10004 ...00 18 e7 09 19 f9 ...... Realtek RTL8169/8110 Family
>>> Gigabit Ethernet
>>> NIC #3
>>> ================================================== =========================
>>>
>>> ================================================== =========================
>>>
>>> Active Routes:
>>> Network Destination Netmask Gateway Interface
>>> Metric
>>> 0.0.0.0 0.0.0.0 192.168.1.1
>>> 192.168.1.100 20
>>> 127.0.0.0 255.0.0.0 127.0.0.1
>>> 127.0.0.1 1
>>> 172.16.1.0 255.255.255.0 172.16.1.1
>>> 172.16.1.1 2
>>> 172.16.1.1 255.255.255.255 127.0.0.1
>>> 127.0.0.1 2
>>> 172.16.1.2 255.255.255.255 172.16.1.1
>>> 172.16.1.1 1
>>> 172.16.1.3 255.255.255.255 172.16.1.1
>>> 172.16.1.1 1
>>> 172.16.255.255 255.255.255.255 172.16.1.1
>>> 172.16.1.1 2
>>> 192.168.1.0 255.255.255.0 192.168.1.100
>>> 192.168.1.100 20
>>> 192.168.1.100 255.255.255.255 127.0.0.1
>>> 127.0.0.1 20
>>> 192.168.1.255 255.255.255.255 192.168.1.100
>>> 192.168.1.100 20
>>> 224.0.0.0 240.0.0.0 172.16.1.1
>>> 172.16.1.1 2
>>> 224.0.0.0 240.0.0.0 192.168.1.100
>>> 192.168.1.100 20
>>> 255.255.255.255 255.255.255.255 172.16.1.1
>>> 172.16.1.1 1
>>> 255.255.255.255 255.255.255.255 192.168.1.100
>>> 192.168.1.100 1
>>> Default Gateway: 192.168.1.1
>>> ================================================== =========================
>>>
>>> Persistent Routes:
>>> Network Address Netmask Gateway Address Metric
>>> 172.16.1.2 255.255.255.255 172.16.1.1 1
>>> 172.16.1.3 255.255.255.255 172.16.1.1 1
>>>
>>> -------- END ---------
>>>
>>
>> I'm guessing it all worked fine before you decided to "move database
>> traffic off the router"?
>>
>> Put it back the way it was. There are some fundamental flaws in your
>> network design.
>>
>> 1) Traffic going from server to server doesn't touch your router.
>> Traffic will only hit the router if it's destined for the Internet.
>>
>> 2) Everything behind the router is considered the "internal network"
>> The 192.168.x.x network is not publicly addressable, cannot be reached
>> from the Internet and therefore is internal only.
>>
>> 3) It looks like you've created static routes on one of those
>> servers. That is also unnecessary and could be where the issue lies.
>> Static routes are needed only when traversing a router. Since there
>> is no router between the local servers, static routes are not necessary.
>>
>> Your network topology should look like this:
>>
>> --------+ +-----------+
>> Router |-----------| Switch |
>> --------+ +-----------+
>> |
>> |
>> ----------+-----------
>> | | |
>> | | |
>> | | |
>> +--------+ +--------+ +--------+
>> | Win 03 | | Win 03 | | Win 03 |
>> | Server | | Server | | Server |
>> | Std x64| | Web Ed.| | Web Ed.|
>> +--------+ +--------+ +--------+
>>
>>
>> Just do something simpler like that and I will bet that your network
>> issues disappear.
>
>
> Actually on second thought, I take back what I said about only needing
> static routes to traverse a router. But if you redesign the network the
> way I showed you, you won't need static routes, and you'll have a much
> simpler and less problematic network.
>
> --cheers

On May 30, 7:22 am, grep <g...@grepster.grep> wrote:
> James: Don't know why you took it back, 'cause effectively, you were
> right the first time.
>
> rlw:
>
> You don't need a static route to reach a network to which you're
> directly connected. So if you have a NIC in the 172.16.1.0 network, it
> serves no purpose to have a route to that network configured.
>
> You also have some screwy things going on in your routing table - like
> routing 127.0.0.1 to 172.16.1.2 at one point?!
>
> James is right, though, about the design. Especially since, with no
> metrics or hard-coded IP addresses in your application code to tell them
> otherwise, there's no way for you to guarantee which path the traffic
> will take between the machines anyway.
>
> Keep it simple.
>
> grep
>
> James Beukelman wrote:
> > James Beukelman wrote:
>
> >> r...@ti.com wrote:
>
> >>> I am a network rookie, and have been stuck for days. Would greatly
> >>> appreciate assistance in getting unstuck or at least pointed in the
> >>> right direction. Everything works fine for a while but eventually I
> >>> lose the ability to connect to the internet from one (and only one)
> >>> computer. Here's a visual of my network setup/configuration:
>
> >>> Internet (static ip)
> >>> |
> >>> |
> >>> +--------+ 192.168.1.1
> >>> | Router |--------------+-----------------+-----------------+
> >>> +--------+ | | |
> >>> |192.168.1.100 |192.168.1.2 |
> >>> 192.168.1.3
> >>> +--------+ +--------+ +--------+
> >>> | Win 03 | | Win 03 | | Win 03 |
> >>> | Server | | Server | | Server |
> >>> | Std x64| | Web Ed.| | Web Ed.|
> >>> +--------+ +--------+ +--------+
> >>> |172.16.1.1 |172.16.1.2 |
> >>> 172.16.1.3
> >>> | | |
> >>> | +--------+ |
> >>> +-------------| Switch |------------+
> >>> +--------+
>
> >>> Each server has two Nic cards. The router is a standard Actiontec
> >>> MI424WR received with my Fios service. The switch is a D-Link Giabit
> >>> (DGS-2205). Sql Server is running on the Win Server Std. The other
> >>> two machines are worker bees and only run server so they'll have
> >>> access to a TCPIP stack that hasn't been handicapped; their primarily
> >>> is to retrieve intellegence from the web and make updates to the
> >>> database (on the Std Sever).
>
> >>> The intent of adding the switch was several fold: 1) get database
> >>> traffic off the router and 2) limit SQL Server access to only the
> >>> internal network. Everything works fine for a while. However, some
> >>> period of time after beginning database updates (e.g. 172.16.1.2 ->
> >>> 172.16.1.1) the Std Server loses it's ability to connect to the
> >>> internet (via web browser or .Net). When this occurs external
> >>> addresses (i.e. on the Internet) can still be found via ping and
> >>> tracert from the Std Server and access on the worker bees is fine/
> >>> unimpeded. It's only the Std Server that's affected. I've found
> >>> nothing to resolve the issue short of rebooting the Router or
> >>> rebooting the Std Server (and doing either seems to resolve the
> >>> issue). Strange, no?
>
> >>> Here's some more background:
> >>> The Std Server is running SP2 and is not a domain controller or
> >>> running DNS (DNS was configured at one point). There is only a single
> >>> gateway configured (192.168.1.1) which is on the Nic's connected to
> >>> 192.168.0.0 network. The Nic's for the 172.16.0.0 network are
> >>> configured without a gateway, defined with static routes (are these
> >>> correct?), have all protocols except TCPIP disabled (e.g. MS Network)
> >>> and "Register this connection's addresses in DNS" is unchecked.
>
> >>> IPCONFIG /all and route PRINT are included below:
>
> >>> IPCONFIG /all:
> >>> -------------
> >>> Windows IP Configuration
>
> >>> Host Name . . . . . . . . . . . . : leed
> >>> Primary Dns Suffix . . . . . . . : 140.com
> >>> Node Type . . . . . . . . . . . . : Unknown
> >>> IP Routing Enabled. . . . . . . . : No
> >>> WINS Proxy Enabled. . . . . . . . : No
> >>> DNS Suffix Search List. . . . . . : 140.com
>
> >>> Ethernet adapter Local Area Connection:
>
> >>> Connection-specific DNS Suffix . :
> >>> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
> >>> Ethernet
> >>> Physical Address. . . . . . . . . : 00-13-72-3D-88-8A
> >>> DHCP Enabled. . . . . . . . . . . : No
> >>> IP Address. . . . . . . . . . . . : 192.168.1.100
> >>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >>> Default Gateway . . . . . . . . . : 192.168.1.1
> >>> DNS Servers . . . . . . . . . . . : 192.168.1.1
>
> >>> Ethernet adapter Local Area Connection 4:
>
> >>> Connection-specific DNS Suffix . :
> >>> Description . . . . . . . . . . . : Realtek RTL8169/8110 Family
> >>> Gigabit Ether
> >>> net NIC #3
> >>> Physical Address. . . . . . . . . : 00-18-E7-09-19-F9
> >>> DHCP Enabled. . . . . . . . . . . : No
> >>> IP Address. . . . . . . . . . . . : 172.16.1.1
> >>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >>> Default Gateway . . . . . . . . . :
>
> >>> route PRINT:
> >>> -----------
>
> >>> IPv4 Route Table
> >>> ================================================== =========================
>
> >>> Interface List
> >>> 0x1 ........................... MS TCP Loopback interface
> >>> 0x10003 ...00 13 72 3d 88 8a ...... Broadcom NetXtreme Gigabit
> >>> Ethernet
> >>> 0x10004 ...00 18 e7 09 19 f9 ...... Realtek RTL8169/8110 Family
> >>> Gigabit Ethernet
> >>> NIC #3
> >>> ================================================== =========================
>
> >>> ================================================== =========================
>
> >>> Active Routes:
> >>> Network Destination Netmask Gateway Interface
> >>> Metric
> >>> 0.0.0.0 0.0.0.0 192.168.1.1
> >>> 192.168.1.100 20
> >>> 127.0.0.0 255.0.0.0 127.0.0.1
> >>> 127.0.0.1 1
> >>> 172.16.1.0 255.255.255.0 172.16.1.1
> >>> 172.16.1.1 2
> >>> 172.16.1.1 255.255.255.255 127.0.0.1
> >>> 127.0.0.1 2
> >>> 172.16.1.2 255.255.255.255 172.16.1.1
> >>> 172.16.1.1 1
> >>> 172.16.1.3 255.255.255.255 172.16.1.1
> >>> 172.16.1.1 1
> >>> 172.16.255.255 255.255.255.255 172.16.1.1
> >>> 172.16.1.1 2
> >>> 192.168.1.0 255.255.255.0 192.168.1.100
> >>> 192.168.1.100 20
> >>> 192.168.1.100 255.255.255.255 127.0.0.1
> >>> 127.0.0.1 20
> >>> 192.168.1.255 255.255.255.255 192.168.1.100
> >>> 192.168.1.100 20
> >>> 224.0.0.0 240.0.0.0 172.16.1.1
> >>> 172.16.1.1 2
> >>> 224.0.0.0 240.0.0.0 192.168.1.100
> >>> 192.168.1.100 20
> >>> 255.255.255.255 255.255.255.255 172.16.1.1
> >>> 172.16.1.1 1
> >>> 255.255.255.255 255.255.255.255 192.168.1.100
> >>> 192.168.1.100 1
> >>> Default Gateway: 192.168.1.1
> >>> ================================================== =========================
>
> >>> Persistent Routes:
> >>> Network Address Netmask Gateway Address Metric
> >>> 172.16.1.2 255.255.255.255 172.16.1.1 1
> >>> 172.16.1.3 255.255.255.255 172.16.1.1 1
>
> >>> -------- END ---------
>
> >> I'm guessing it all worked fine before you decided to "move database
> >> traffic off the router"?
>
> >> Put it back the way it was. There are some fundamental flaws in your
> >> network design.
>
> >> 1) Traffic going from server to server doesn't touch your router.
> >> Traffic will only hit the router if it's destined for the Internet.
>
> >> 2) Everything behind the router is considered the "internal network"
> >> The 192.168.x.x network is not publicly addressable, cannot be reached
> >> from the Internet and therefore is internal only.
>
> >> 3) It looks like you've created static routes on one of those
> >> servers. That is also unnecessary and could be where the issue lies.
> >> Static routes are needed only when traversing a router. Since there
> >> is no router between the local servers, static routes are not necessary.
>
> >> Your network topology should look like this:
>
> >> --------+ +-----------+
> >> Router |-----------| Switch |
> >> --------+ +-----------+
> >> |
> >> |
> >> ----------+-----------
> >> | | |
> >> | | |
> >> | | |
> >> +--------+ +--------+ +--------+
> >> | Win 03 | | Win 03 | | Win 03 |
> >> | Server | | Server | | Server |
> >> | Std x64| | Web Ed.| | Web Ed.|
> >> +--------+ +--------+ +--------+
>
> >> Just do something simpler like that and I will bet that your network
> >> issues disappear.
>
> > Actually on second thought, I take back what I said about only needing
> > static routes to traverse a router. But if you redesign the network the
> > way I showed you, you won't need static routes, and you'll have a much
> > simpler and less problematic network.
>
> > --cheers

Thanks guys, I greatly appreciate the helping hand. First a couple
additional tidbits/factors:

1. combined traffic to/from database and internet was sufficient to
cause TCPIP collisions and subsequent throttling by the TCPIP stacks.
2. all traffic on the internal network (e.g. to the database) is
database specific traffic (does not require internet access) and is
handled via hard-coded IP addresses in the application code

So on your first and second point James, those are as intended. The
additional thinking on your second point was security related; that is
having SQL Server only accessible from the internal network.

>From my research on making this work I thought I had to define a
gateway for the 192.168.0.0 network and then define explicit routes on
the internal (172.16.0.0) network (with no gateway).

The guys I work with (who aren't particularly network savvy) suggested
the issue might be in the arp cache as tracert and ping continue to
work even when web browsers and .Net traffic all fails. The hole with
this theory is that flushing arpcache seems to have no effect. They
did suggest it might be possible to bypass TCPIP routing altogether
and map the mac addresses directly within the arpcache (don't know if
this is possible).

This would seem to be such a basic configuration that I'm starting to
think this may a Microsoft marketing (i.e. crippleware) issue. Maybe
I need to upgrade to the Enterprise versions of SQL Server for this to
work?

TIA for additional insights...