none
Gremlins - under Static IP can't reach Gateway - under DHCP works fine - use DHCP as Static address, can't reach DNS? - HUH?

    Question

  • Ok

    My current Static is:

    Local       172.17.250.253
    Subnet     255.255.0.0
    Gateway  172.17.0.1
    Dns1       192.168.20.6
    Dns2       67.17.215.132

     

    If i set it up as static I can't ping the gateway, DHCP works fine. So I have been running it as DHCP till I have a bit more time.

    The only Difference Static and DHCP is the last two Octets of the local address.

    I tried to set up the Static address again this after noon, it worked I pinged the gateway twice, went out the browser and nothing, went back and tried to ping again, can't reach address.


    Reset DHCP, it works fine

    So I tried to set the static up to the DHCP address. 

    I can ping the gateway, but can't ping either DNS servers?

    I'm back to running DHCP.

    OS - 2008 Server Std, fresh load, All Updates and SP2.

    Ran this past My ISP and he says his numbers look good.

    HUH?

    Hami

    Saturday, January 01, 2011 1:17 AM

All replies

  • Hello Hami,

    It appears that you abandoned your original posting and that this is a duplicate one: http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/662e03ae-bca0-4059-99f0-c9930b4dac03/

    So I assume that you have validated that it is not a network driver issue.  In the original posting you mentioned that the router was actually a server.  Have you checked that your routing table on that server/router is correct.  An incorrect routing table could affect the ability for the packets to return back to the client.

    You may want to install a packet capture application both on this computer and the server to see where the packets are actually going (Wireshark is a good application and its free).  However, I would first validate that the server (router's) routing table is correct.  While I understand that it works for IPs in the DHCP range, it does not work for the IPs in the static range.  You can check to see if this is a symptom by just assigning (temporarily) an IP from the DHCP range, statically on the server.  If the problem persists, then it would not be a routing issue on the router (an IP is an IP regardless if its DHCP or statically assigned).  If the DHCP IP assigned statically still causes an issue, I would definately look at the router and/or run some packet captures.

     


     

    Visit: anITKB.com, an IT Knowledge Base.

    Saturday, January 01, 2011 7:47 PM
  • Yeh, I thunk, it might get a better response in a forum with the Network in the description?

     

    I updated all the network drivers (one set were Marvel, and the other were Realtek), and it not working.

     

    Yes the router is a server, its a third party app. All of the testing is with the app shut down.

     

    I did try to use a DHCP address, I set it up as DHCP, got a address, reset the address to static (using the DHCP address), and the symptoms changed.  With the true static address, I could not reach the Gateway, with the DHCP static address I could reach the Gateway but could not reach the DNS.

    In the last line you refer to the router, your referring to the ISP router, I keep my router app offline during the testing. 

    I'm going to D/L the capture app and take a looksee.

     

    Back soon

    Hami

     

     

    Saturday, January 01, 2011 8:34 PM
  • Ok, new info!

     

    When it works the traffic goes out the first Nic. 

    And when it fails it goes out Nic 2.

    the firs nics gateway is 172.17.0.1, this is the address I'm pinging.

     

    If i disable the second Nic, it goes nowhere! and fails!

     

    Any ideas on a fix?

     

    Hami

    Saturday, January 01, 2011 10:08 PM
  • first, second NIC?  If you can provide a simple diagram that would be helpful. 
    Visit: anITKB.com, an IT Knowledge Base.
    Sunday, January 02, 2011 4:16 AM
  • It is really simple, a 2008 box with two Nic's.

     

    Nic one is connected to the outside world, it can either pull a DHCP address, or a static address.

    Local  172.17.250.253  if it is DHCP 172.17.xxx.xxx, the rest stays the same.

    Subnet 255.255.0.0

    Gateway 172.17.0.1

    and two DNS's

     

    Nic two is connected to the private Internal network.

    Local 192.168.xxx.xxx

    Subnet 255.255.255.0

    Gateway 192.168.xxx.1

     

    The router app is offline.

    if i set it up on DHCP it works fine and I can ping the gateway and get to the internet

    If I set to a static IP, I get one maybe two sets of Pings to the gateway, and then it is unreachable.

    watching the traffic I can see the first sets of pings go out and come back fine.

    after it fails, if I go to the Nic 2 and watch the traffic, I see the ping go out, but no return.

     

    Hope this helps

    Hami

     

     

     

     

    Sunday, January 02, 2011 4:40 AM
  •   You can only have one gateway per machine, not one per NIC. If your "public" NIC gets a gateway from DHCP, the "private" NIC gateway setting should be blank.

     


    Bill
    Monday, January 03, 2011 1:28 AM
  • A few gapes being filled in my knowledge base. 

     

    OK removed second gateway address, no change, it's gotta be something something simple/stupid?

     

    Hami

    Monday, January 03, 2011 5:42 AM
  • Hi Hami,

     

    Could you post the route table and ipconfig /all result here for further investigation ?

    Are there any server or scope options set on DHCP server ?

    I suspect this may a routing issue. Like Bill mentioned only one default gateway should be configured on any multihomed computer.

     

    Default Gateway Configuration for Multihomed Computers

    http://support.microsoft.com/kb/157025

     

    Thanks.

     

    Tiger Li


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, January 03, 2011 7:38 AM
  • Here it is.DHCP, Nic 2 disabled

    Microsoft Windows [Version 6.0.6002]
    Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

    C:\Users\Administrator>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : Router-1
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : multicable.com.mx

    Ethernet adapter Local Area Connection 2:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller #2
       Physical Address. . . . . . . . . : 00-1F-C6-45-5C-64
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.69.101(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . : xxxxxxxxxx.com  Blanked out by me
       Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller
       Physical Address. . . . . . . . . : 00-1F-C6-45-5A-7A
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 172.17.12.214(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Lease Obtained. . . . . . . . . . : Sunday, January 02, 2011 9:30:55 PM
       Lease Expires . . . . . . . . . . : Sunday, January 09, 2011 9:30:59 PM
       Default Gateway . . . . . . . . . : 172.17.0.1
       DHCP Server . . . . . . . . . . . : 192.168.20.12
       DNS Servers . . . . . . . . . . . : 192.168.20.6
                                           67.17.215.132
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter Local Area Connection* 8:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : xxxxxxxxxx.com  Blanked out by me
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 12:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 11:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 02-00-54-55-4E-01
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:1815:38a6:53ee:f329(Preferred)
       Link-local IPv6 Address . . . . . : fe80::1815:38a6:53ee:f329%10(Preferred)
       Default Gateway . . . . . . . . . : ::
       NetBIOS over Tcpip. . . . . . . . : Disabled

    C:\Users\Administrator>


    Static nic 2 disabled

    Microsoft Windows [Version 6.0.6002]
    Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

    C:\Users\Administrator>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : Router-1
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : multicable.com.mx

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . : xxxxxxxxxx.com  Blanked out by me
       Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller
       Physical Address. . . . . . . . . : 00-1F-C6-45-5A-7A
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 172.17.12.214(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Lease Obtained. . . . . . . . . . : Sunday, January 02, 2011 9:30:55 PM
       Lease Expires . . . . . . . . . . : Sunday, January 09, 2011 9:30:58 PM
       Default Gateway . . . . . . . . . : 172.17.0.1
       DHCP Server . . . . . . . . . . . : 192.168.20.12
       DNS Servers . . . . . . . . . . . : 192.168.20.6
                                           67.17.215.132
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter Local Area Connection* 8:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : xxxxxxxxxx.com  Blanked out by me
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 11:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 02-00-54-55-4E-01
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:1815:38a6:53ee:f329(Preferred)
       Link-local IPv6 Address . . . . . : fe80::1815:38a6:53ee:f329%10(Preferred)
       Default Gateway . . . . . . . . . : ::
       NetBIOS over Tcpip. . . . . . . . : Disabled

    C:\Users\Administrator>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : Router-1
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller
       Physical Address. . . . . . . . . : 00-1F-C6-45-5A-7A
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 172.17.250.253(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . : 172.17.0.1
       DNS Servers . . . . . . . . . . . : 192.168.20.6
                                           67.17.215.132
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter Local Area Connection* 8:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 11:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 02-00-54-55-4E-01
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    C:\Users\Administrator>ping 172.17.0.1

    Pinging 172.17.0.1 with 32 bytes of data:
    Request timed out.
    Request timed out.
    Reply from 172.17.250.253: Destination host unreachable.
    Reply from 172.17.250.253: Destination host unreachable.

    Ping statistics for 172.17.0.1:
        Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

    C:\Users\Administrator>


    DHCP router table


    Microsoft Windows [Version 6.0.6002]
    Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

    C:\Users\Administrator>route print
    ===========================================================================
    Interface List
     14 ...00 1f c6 45 5a 7a ...... Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller
      1 ........................... Software Loopback Interface 1
     18 ...00 00 00 00 00 00 00 e0  Microsoft ISATAP Adapter
     10 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
    ===========================================================================

    IPv4 Route Table
    ===========================================================================
    Active Routes:
    Network Destination        Netmask          Gateway       Interface  Metric
              0.0.0.0          0.0.0.0       172.17.0.1     172.17.12.20     60
            127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
            127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
      127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
           172.17.0.0      255.255.0.0         On-link      172.17.12.20    286
         172.17.12.20  255.255.255.255         On-link      172.17.12.20    286
       172.17.255.255  255.255.255.255         On-link      172.17.12.20    286
            224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
            224.0.0.0        240.0.0.0         On-link      172.17.12.20    286
      255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      255.255.255.255  255.255.255.255         On-link      172.17.12.20    286
    ===========================================================================
    Persistent Routes:
      None

    IPv6 Route Table
    ===========================================================================
    Active Routes:
     If Metric Network Destination      Gateway
     10     38 ::/0                     On-link
      1    306 ::1/128                  On-link
     10     38 2001::/32                On-link
     10    286 2001:0:4137:9e76:241e:2f2d:53ee:f3eb/128
                                        On-link
     10    286 fe80::/64                On-link
     10    286 fe80::241e:2f2d:53ee:f3eb/128
                                        On-link
      1    306 ff00::/8                 On-link
     10    286 ff00::/8                 On-link
    ===========================================================================
    Persistent Routes:
      None

    C:\Users\Administrator>

    Route table static


    Microsoft Windows [Version 6.0.6002]
    Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

    C:\Users\Administrator>route print
    ===========================================================================
    Interface List
     14 ...00 1f c6 45 5a 7a ...... Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller
      1 ........................... Software Loopback Interface 1
     18 ...00 00 00 00 00 00 00 e0  Microsoft ISATAP Adapter
     10 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
    ===========================================================================

    IPv4 Route Table
    ===========================================================================
    Active Routes:
    Network Destination        Netmask          Gateway       Interface  Metric
              0.0.0.0          0.0.0.0       172.17.0.1   172.17.250.253    286
            127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
            127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
      127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
           172.17.0.0      255.255.0.0         On-link    172.17.250.253    286
       172.17.250.253  255.255.255.255         On-link    172.17.250.253    286
       172.17.255.255  255.255.255.255         On-link    172.17.250.253    286
            224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
            224.0.0.0        240.0.0.0         On-link    172.17.250.253    286
      255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      255.255.255.255  255.255.255.255         On-link    172.17.250.253    286
    ===========================================================================
    Persistent Routes:
      Network Address          Netmask  Gateway Address  Metric
              0.0.0.0          0.0.0.0       172.17.0.1  Default
    ===========================================================================

    IPv6 Route Table
    ===========================================================================
    Active Routes:
     If Metric Network Destination      Gateway
     10     38 ::/0                     On-link
      1    306 ::1/128                  On-link
     10     38 2001::/32                On-link
     10    286 2001:0:4137:9e76:38d3:3685:53ee:502/128
                                        On-link
     10    286 fe80::/64                On-link
     10    286 fe80::38d3:3685:53ee:502/128
                                        On-link
      1    306 ff00::/8                 On-link
     10    286 ff00::/8                 On-link
    ===========================================================================
    Persistent Routes:
      None

    C:\Users\Administrator>ping 172.17.0.1

    Pinging 172.17.0.1 with 32 bytes of data:
    Reply from 172.17.250.253: Destination host unreachable.
    Reply from 172.17.250.253: Destination host unreachable.
    Reply from 172.17.250.253: Destination host unreachable.
    Reply from 172.17.250.253: Destination host unreachable.

    Ping statistics for 172.17.0.1:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    C:\Users\Administrator>


    and a bit more, some traffic in the next post

    Hami

     

    P.S. a interesting note when I change from DHCP to Static I can ping a few times and it works, then it fails!

    Monday, January 03, 2011 8:49 AM
  • Hello Hami,

    This is definately likely to be a routing issue.  While reviewing the information above, it seems that you have other components on your network that you have not described as of yet.  For instance, you have addresses referred above to 192.168.20.x and 192.168.69.x.  It would really help if you would provide a high level network design.  Its not clear on how your network is designed based on the configuration and routing table listed above.

    Also, there is no need to mask ('x' out) any of your internal IP addresses.  Having your internal IP scheme doesnt really increase any security risks since we do not know your public IP address.  It makes it harder to understand your layout.  However, post whatever is within your comfort level.

     

     


    Visit: anITKB.com, an IT Knowledge Base.
    Monday, January 03, 2011 3:44 PM
  • Ok

     

    192.168.20.xxx is on the public side (my ISP) it is the DNS server 192.168.20.6  and the DHCP server 192.168.20.12, info in IPCONFIG

    192.168.69.xxx is my private side and currently the address are cleared and the Nic is disabled. Info listed in earlier text

    the blanked out was not a IP address it was a URL of my ISP, the rest of the xxx are a variable address or should have been listed a 0 showing a network.

     

    at this point it is not even a network, it is a 2008 server trying to connect to the internet with Via a static address.

     

    I have taken out all/any things that could make things complex/confusing, start with the simple, get it to work, add till it fail, fix it add more complexity.

     

    I'm not hiding anything, there is no high level of design, it is a box tiring to connect to the internet.

     

    Hami

    Monday, January 03, 2011 7:21 PM
  • Hello Hami,

    So is it safe to assume that your network design looks like this (http://i56.tinypic.com/2ywv5nc.png)?

    Are the IPs 192.168.20.6 and 192.168.20.12 other servers in the yellow zone pictured above or one on the server/router and the other IP the ISP Modem/Router?  So with this design and the config listed above, you should be able ping 172.17.0.1 from 172.17.20.253 regardless whether the IP config is static (172.17.20.253/16) or dynamic (172.17.12.214/16)on the server.  If you are still unable to ping the gateway from the server these are the things you have to verify:

    1) on the server, the gateway's (172.17.0.1) MAC address must be listed in the arp cache (arp -a)
    2) On the server/router, the 172.17.0.1 NIC interface should not have a default gateway listed.  ONly the 192.168.20.x interface should have a gateway listed.
    3) Review the server/router's Routing table.  There should be a clear indication that to get to the 172.17.x.x network, the packet must leave through the 172.17.0.1 interface.
    4) Review the server's routing table.  There should be a clear indication that to get to the 172.17.x.x network, the packet must leave through the 172.17.20.253 or 172.17.12.214 interface depnding on the IP you have configured.

    Make sure that your Network Driver on the server is correct and up to date.  Do the same for the server/router.

     

     


    Visit: anITKB.com, an IT Knowledge Base.
    Monday, January 03, 2011 8:11 PM
  • I will go thru and check all that you ask.

     

    Maybe I don't understand, but let me explain how this is put together.

     

    Server 1 (the only one)

    Nic               DHCP                    Static                  status

     1 

    Local        172.17.xxx.xxx     172.17.250.253       Enabled

    Subnet     255.255.0.0           255.255.0.0

    Gateway   172.17.0.1            172.17.0.1

    DNS1       192.168.20.6        192.168.20.6

    DNS2       67.17.215.132       67.17.215.132

    DHCP       192.168.20.12        NA

     

      2

    Disabled

     

    Asustek Server loaded 2008 STD Server (fresh default load)

     

    The Asustek server is connected to a cable modem, this is all there is on my side, nothing else.

     

    The Gateway, DNS's, the DHCP server are all on the ISP's side.

     

    Now the trace route to 172.17.0.1

    Tracing route to 172.17.0.1 over a maximum of 30 hops

      1     5 ms     7 ms    12 ms  172.17.0.1

     

    now going thru Wireshark and CMD line pings.  I have a tracking of 28 pings (7 sets) and only 20 (5 sets) show up on Wireshark, the last 8 pings (2 sets) fail.

    if there is some means to get these to you, E-mail, I can set up a FTP server, or you can remote in?

     

    hami

     

     

     

     

     

    Monday, January 03, 2011 8:58 PM
  • Ok, so your network diagram looks like this (http://i52.tinypic.com/eiwa6g.png)?  If so, there is no need to worry about the 192.168.20.x network. 

    This makes things very simple.  To summarize, a DHCP or static IP address should not affect your ability to access the gateway. 

    Here are some new comments...diregard the previous ones.

    1) on the server, the gateway's (172.17.0.1) MAC address must be listed in the arp cache (arp -a)
    2) Make sure the server has the correct and up to date Network Driver.  Check with the vendor.
    3) Make sure you do not have a faulty network cable.  A faulty network cable could result in intermittent issues.
    4) Make sure you do not have an issue with the switch/router network port.  A bad port or port mismatch (Autonegotiate/Autosense) could result in intermittent issues.
    5) PING uses ICMP.  ICMP is usually treated with the lowest priority by network switches and routers.  A failed ICMP does not mean that there is an actual issue.  However, I do not think this is your case.  You clearly have another issue.
    6) Does this problem happen with another network card?  Can you plug in a different card/brand of card and see if the problem is reproduced?


    Visit: anITKB.com, an IT Knowledge Base.
    Monday, January 03, 2011 9:14 PM
  • Ok

     

    2)     All drivers are up to date.

    3)     there failures are tied absolutely to the changing from DHCP to and from Static, no cable issue.

    4)     there is one cable from the Asustek to the modem.

    5)     They are the black sheep in the network world, but there is another problem.

    6)     Even better it happens with another box, nothing similar than Operating System?

     

    Did you get the part about the traces, I sent out 28 pings and only 20 were captured by wireshark leaving the system ! I have the trace files.

     

    Hami

     

    Monday, January 03, 2011 9:52 PM
  • I just moved a xp box in the place of the 2008 server, and it has no problems connecting and maintaining connection.

     

    Hami

    Monday, January 03, 2011 11:06 PM
  • Replacing the box with another computer is a real good test as you have determined that there is nothing wrong with the network or modem.  So it appears that the problem is tied to that server.

    I can tell you that there is nothing special in a configuration that needs to be done when switching from DHCP to static.  If you have hard coded in the correct settings, IP, Subnet Mask and Gateway, then you should most definately be able to send simple PING packets back and forth.

    If that is not happening, there is something wrong with the driver, TCP/IP stack, or some weird failure in the OS.

    You can try to remove the NIC device from Device manager.  that has worked for others in the past for similar issues.  If you have another Network Card, I would install it and try that.  If it continues to fail, that rules out the NIC and driver concern.  With most problems, at some point in time you may have to decide to wipe the system and do a clean install. 

    I think this issue has been thoroughly investigated.  You may or may not be able to find the culprit.  If you feel like you want to invest additioanl time, try to install another NIC with new drivers.  Other than that, I would probably clasify this issue as an Outlier.

    I wish I could provide you with more feedback.  I would be interested in knowing what the issue is if you do come accross a final solution.

     


    Visit: anITKB.com, an IT Knowledge Base.
    Tuesday, January 04, 2011 1:12 AM
  • Current status.

     

    Loaded 2008 R2 on other partition, and responds the same, I added a XP box to the subnet and it seams to work fine.

     

    So the question is how dose XP/2008 handle DHCP/Static differently.

     

    I going to burn 2008 R2 and load XP on the same box for more of a comparison.  Will get back after install

     

    Hami

    Wednesday, January 05, 2011 4:09 AM
  • I have had almost this exact same problem and at this point I believe it to be something with a core OS function or the NIC itself.  I think all of the analysis of route tables, etc., is essentially not related.  In my case, I have Windows 2008 Server (64 bit) running on a Gateway PC (I know - not optimal...) that has an onboard Realtek RTL8168 Family PCIe GB adapter.  Upon installation of the OS, the device showed up correctly recognized by name in Device Manager, but with an error condition relating to the driver.  I installed the only compatible driver I could find, a Vista 64 bit driver directly from Realtek's site.  The card works, but with this mysterious behavior.

    When the card first initializes with the new driver, it is obviously by default a DHCP client.  The card leases an IP from my DHCP server without incident and I have full connectivity (local and remote) with no issues.  However, I want to use a static IP for this server.  So, I configure the static address I want - all parameters such as gateway, DNS, etc. checked again and again and only have "local" connectivity.  In my case, I can ping the gateway, ping DNS, even resolve external names via nslookup without any problem - but still only "local" connectivity.  The ONLY way I can get this to work as I want is if I make the assigned static address the EXACT SAME address as what was originally assigned to it via DHCP.  Then, I have full connectivity.  It is crazy and completely without logic.  I went into my DHCP and put in an exclusion range to keep it from issuing this one "good" address to any other device.

    It's almost as if somehow the original DHCP acquired address is somehow bound to the NIC permanently.  Maybe something with the chipset of this particular NIC?  I'm glad it works now, but it's a little inconvenient to have to assign a static from within my DHCP pool of addresses.

    Wednesday, January 05, 2011 6:20 PM
  • This issue shouldn't be troubleshoot any longer as an IP Configuration, or routing issue.  There has been enough testing and discussion, in my opinion, which indicates that the issue is a problem with the OS/Driver combination.

    I suspect that when XP is loaded on this computer, all will work as expected.  If it does not, it could be a hardware issue.  The typical troubleshooting process deals with IP config first since its easy to check and that is were most of the errors are found.

     


    Visit: anITKB.com, an IT Knowledge Base.
    Wednesday, January 05, 2011 6:50 PM
  • Sound pretty much the same to me, but after a few min the pinging of the gateway goes away. So check it again.

    It is my understanding 2008 and vista share the same base core and the drivers work, just as 2003/XP, and 2008 R2/Windows 7.

     

    Ok I reloaded the same system with a copy of XP Pro and it runs fine with both DHCP and Static addresses.

     

    So Far it point to the OS (2008 Std Server)

     

    Oh, my other server used realtek Nic's, it was the same, this one uses Marvel.

     

    Hami

     

    Wednesday, January 05, 2011 6:51 PM
  • Jm

     

    so based on this how can we get this thread moved to a OS forum, there needs to be the history?

     

    Hami

    Wednesday, January 05, 2011 6:56 PM
  • A moderator can move the thread.  However, if you open a new thread, you can at least reference this one by the URL. 

    Since the problem does appear to be OS/Driver related, I would try to use an Intel, HP, or other similar brand for production servers.  If changing the NIC works, its clearly a driver issue.  You would then have to take up that issue with the vendor.

    One thing that is important for Windows Operating systems is to make sure the hardware you are using in on the Hardware Compatibility List (HCL) and its certified for the OS.  The cards you are using may not be. 

    http://www.windowsservercatalog.com
     


    Visit: anITKB.com, an IT Knowledge Base.
    Wednesday, January 05, 2011 7:09 PM
  • JM

     

    The box is a Asustek Server. I had originally believed it was assembled here, but it was purchased directly AsusTek.

     

    It is certified for 2003.

     

    Hami

    Wednesday, January 05, 2011 7:54 PM
  • I saw your other threads, and frankly, I'm not sure which to post a response in, so for simplicity sakes, I will keep my responses here.

    It appears that most things have been addressed and tried with help from JM and others. The only thing I couldn't find in this thread, unless I missed it, is what is being used as a DHCP server (192.168.20.12), one of the hardware routers or is it a DHCP server? If a hardware router/firewall, are there any rules blocking any IPs not in the pool? Is it possibly something like QIP or MetaIP?

    Ace


    Ace Fekay
    MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services

    This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    Thursday, January 06, 2011 5:27 AM