Announcement

Collapse
No announcement yet.

Old 2000 Server cannot ping/access WAN

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Old 2000 Server cannot ping/access WAN

    We have a very standard network, we run a Cisco ASA 5505 that connects via a VPN Tunnel to our DataCenter. Local Subnet 192.168.110.x and our DataCenter Subnet is 10.100.10.x and I can ping almost all servers to all workstations, however I have 2 servers that I cannot get to communicate to our DataCenter. The weird thing is that I was able to join them to the new Domain.

    We had our Citrix server along with our Sql server that were part of the olddomain.com and our newdomain.com is now maintained out of our DataCenter. We have a local DC in our branch and it can ping our servers in our DataCenter, however I can not get our Citrix or Sql server to ping or communicate to our DataCenter. I actually have an old webserver that is still on our olddomain.com and it can even ping our datacenter and the Citrix and Sql server are using the same switch as the old web server. I have checked the IP/DNS/WINS/Gateway/Host file and I cannot see any reason why I cannot ping these two machines, all the others are able to communicate so I'm not sure what else to check. Hope this makes sense, please let me know if yo need any other information.

    Server - 2000 Server (Old Citrix server), 2000 Server (Old SQL server) 192.168.110.x

    DataCenter - 10.100.10.x

    Local DC has a trust and our Cisco Firewall does not have any Access List preventing any computers from communicating to our DataCenter.

    Thanks,

  • #2
    Re: Old 2000 Server cannot ping/access WAN

    default gateway or route invalid ?
    Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

    Comment


    • #3
      Re: Old 2000 Server cannot ping/access WAN

      "default gateway or route invalid ?"

      I have checked the gateway, 192.168.110.1 which is the default. Route invalid? Again, I have checked IP subnet/DNS/WINS/Gateway and they are all set correctly. I have compared to other servers and they are find. I can ping all LAN computers and the gateway. I just can't get outside.

      Comment


      • #4
        Re: Old 2000 Server cannot ping/access WAN

        Any ACLS on the router that would block those machines???

        Can you ping by address rather than name???

        Comment


        • #5
          Re: Old 2000 Server cannot ping/access WAN

          There is no list preventing the server from getting out, I actually called TAC and they verified that neither my ASA routers were blocking the server from using the tunnel. They did not know what could be the issue.
          I am using the IP address - 10.100.10.101.

          I know this sounds weird, but I just don't know what it can be. Someone suggested I use WireShark but I'm not finding much from there, it's so complicated for someone with no experience with WireShark.

          Comment


          • #6
            Re: Old 2000 Server cannot ping/access WAN

            IMHO, the best place to start would be to run a trace route from the problem server to the data center. A ping is only going to tell you whether ICMP packets can get from one network to another but it is not going to tell you why if they don't get there. A trace route (tracert) will tell you what path the traffic from the old server to the data center is trying to take. This should give you some idea of where the problem is. Also check the switch, router, or firewall for a stale ARP entry for the problem server.

            Comment


            • #7
              Re: Old 2000 Server cannot ping/access WAN

              Thanks for the response. Sorry I did not mention that I did do a tracert but it did not help.

              Here are the results:

              M:\Documents and Settings\cbadmin>tracert 10.100.10.101
              Tracing route to cb-dc01.newdomain.local [10.100.10.101]
              over a maximum of 30 hops:
              1 * * * Request timed out.
              2 * * * Request timed out.
              3 * * * Request timed out.
              4 ^C
              M:\Documents and Settings\cbadmin>

              so it's getting the right route but it cannot transmit.

              The weird thing is that the FQDN for my server is ccfctx042.newdomain.local.

              I'm going through adding new updates and then I'll test again.

              forgot to mention that I also changed the IP to a DHCP thinking it might be an IP issue but I was still unable to ping.
              Last edited by snteran; 16th December 2009, 17:27.

              Comment


              • #8
                Re: Old 2000 Server cannot ping/access WAN

                OK, so I have done all the updates and still a no go.

                Not sure what else it could be, especially since I setup the DHCP and got a totally new IP. Layer 2 is MAC based, but we don't have our switches configured to do any type of vlan/spanning. Well, I'll keep at it. any ideas, please let me know.

                Comment


                • #9
                  Re: Old 2000 Server cannot ping/access WAN

                  Can you draw your network subnets out so we can visualise the network correctly.

                  Please upload it as a jpeg, png format rather than a .doc.

                  Comment


                  • #10
                    Re: Old 2000 Server cannot ping/access WAN

                    Originally posted by snteran View Post
                    Thanks for the response. Sorry I did not mention that I did do a tracert but it did not help.

                    Here are the results:

                    M:\Documents and Settings\cbadmin>tracert 10.100.10.101
                    Tracing route to cb-dc01.newdomain.local [10.100.10.101]
                    over a maximum of 30 hops:
                    1 * * * Request timed out.
                    2 * * * Request timed out.
                    3 * * * Request timed out.
                    4 ^C
                    M:\Documents and Settings\cbadmin>

                    so it's getting the right route but it cannot transmit.

                    The weird thing is that the FQDN for my server is ccfctx042.newdomain.local.

                    I'm going through adding new updates and then I'll test again.

                    forgot to mention that I also changed the IP to a DHCP thinking it might be an IP issue but I was still unable to ping.
                    Well you've got a DNS problem as well, if you're getting the wrong FQDN back when pinging the ip address.

                    Comment


                    • #11
                      Re: Old 2000 Server cannot ping/access WAN

                      OK, so you will see on the 192 subnet I have put 4 nodes, two of them can ping/transfer to our 10.100.10.x network in our datacenter. Server sql20 and ccfctx042 cannot communicate over the network. However the other two nodes, web80 and dtop20 can ping/transfer, you will notice that the web80 node is still on our old domain.

                      I hope this information helps.

                      As for the dns issue, I am using the IP address so I'm not sure why it would be a dns. Although it did resolve the correct fqdn for the IP address I was pinging.
                      Attached Files
                      Last edited by snteran; 17th December 2009, 21:18.

                      Comment


                      • #12
                        Re: Old 2000 Server cannot ping/access WAN

                        It looks like your not actually getting anywhere from the TRACERT that you've posted, you should at least get to your gateway.

                        Can you post an IPCONFIG /ALL from the affected servers and one from the good servers please.

                        Comment


                        • #13
                          Re: Old 2000 Server cannot ping/access WAN

                          OK, here is a ping from a computer that is still on our old domain that can ping and transfer data and then the below system is the server that is already on the new domain but cannot ping/transfer.


                          C:\Documents and Settings\Administrator.olddomain>ipconfig /all
                          Windows 2000 IP Configuration
                          Host Name . . . . . . . . . . . . : ccfweb080
                          Primary DNS Suffix . . . . . . . : olddomain.com
                          Node Type . . . . . . . . . . . . : Hybrid
                          IP Routing Enabled. . . . . . . . : No
                          WINS Proxy Enabled. . . . . . . . : No
                          DNS Suffix Search List. . . . . . : olddomain.com
                          Ethernet adapter Intel Pro 1000 MT Dual Port Gigabit Ethernet Adapter - PCI slot
                          2 - Link A:
                          Connection-specific DNS Suffix . :
                          Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Dual Port Serve
                          r Adapter
                          Physical Address. . . . . . . . . : 00-04-23-5C-88-70
                          DHCP Enabled. . . . . . . . . . . : No
                          IP Address. . . . . . . . . . . . : 192.168.110.30
                          Subnet Mask . . . . . . . . . . . : 255.255.255.0
                          Default Gateway . . . . . . . . . : 192.168.110.1
                          DNS Servers . . . . . . . . . . . : 192.168.110.14
                          Primary WINS Server . . . . . . . : 192.168.110.1

                          ************************************************** ************************
                          Below system cannot ping/transfer to our WAN. (10.100.10.x)
                          M:\Documents and Settings\cbadmin>ipconfig /all
                          Windows 2000 IP Configuration
                          Host Name . . . . . . . . . . . . : ccfctx042
                          Primary DNS Suffix . . . . . . . : newdomain.local
                          Node Type . . . . . . . . . . . . : Hybrid
                          IP Routing Enabled. . . . . . . . : No
                          WINS Proxy Enabled. . . . . . . . : No
                          DNS Suffix Search List. . . . . . : newdomain.local
                          Ethernet adapter Local Area Connection:
                          Connection-specific DNS Suffix . : newdomain.local
                          Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE
                          (NDIS VBD Client)
                          Physical Address. . . . . . . . . : 00-18-8B-35-AE-12
                          DHCP Enabled. . . . . . . . . . . : Yes
                          Autoconfiguration Enabled . . . . : Yes
                          IP Address. . . . . . . . . . . . : 192.168.110.234
                          Subnet Mask . . . . . . . . . . . : 255.255.255.0
                          Default Gateway . . . . . . . . . : 192.168.110.1
                          DHCP Server . . . . . . . . . . . : 192.168.110.14
                          DNS Servers . . . . . . . . . . . : 192.168.110.14
                          192.168.110.10
                          Primary WINS Server . . . . . . . : 192.168.110.1
                          Lease Obtained. . . . . . . . . . : Sunday, December 20, 2009 10:01:44 P
                          M
                          Lease Expires . . . . . . . . . . : Monday, December 21, 2009 10:01:44 P
                          M

                          Comment


                          • #14
                            Re: Old 2000 Server cannot ping/access WAN

                            Can the affected machine ping an address on the same LAN??

                            Can the affected machine ping the gateway???

                            Can the affected machine actually get past the gateway?? I'm presuming you use this to connect to the internet. Try pinging a google address.

                            Comment


                            • #15
                              Re: Old 2000 Server cannot ping/access WAN

                              sorry for the delay in my response, I have been on vacation.

                              First Ping is to our gateway.
                              Second ping is to my workstation
                              Third ping is to Google
                              Forth ping is to our DataCenter network.

                              Just does not make any sense to me how this is possible. I sure would love to figure this one out.

                              M:\Documents and Settings\cbadmin>ping 192.168.110.1
                              Pinging 192.168.110.1 with 32 bytes of data:
                              Reply from 192.168.110.1: bytes=32 time=1ms TTL=255
                              Reply from 192.168.110.1: bytes=32 time=1ms TTL=255
                              Reply from 192.168.110.1: bytes=32 time=1ms TTL=255
                              Reply from 192.168.110.1: bytes=32 time<10ms TTL=255
                              Ping statistics for 192.168.110.1:
                              Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
                              Approximate round trip times in milli-seconds:
                              Minimum = 0ms, Maximum = 1ms, Average = 0ms
                              M:\Documents and Settings\cbadmin>ping 192.168.110.25
                              Pinging 192.168.110.25 with 32 bytes of data:
                              Reply from 192.168.110.25: bytes=32 time<10ms TTL=128
                              Reply from 192.168.110.25: bytes=32 time<10ms TTL=128
                              Reply from 192.168.110.25: bytes=32 time<10ms TTL=128
                              Reply from 192.168.110.25: bytes=32 time<10ms TTL=128
                              Ping statistics for 192.168.110.25:
                              Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
                              Approximate round trip times in milli-seconds:
                              Minimum = 0ms, Maximum = 0ms, Average = 0ms
                              M:\Documents and Settings\cbadmin>ping google.com
                              Pinging google.com [74.125.155.103] with 32 bytes of data:
                              Reply from 74.125.155.103: bytes=32 time=15ms TTL=53
                              Reply from 74.125.155.103: bytes=32 time=14ms TTL=53
                              Reply from 74.125.155.103: bytes=32 time=14ms TTL=53
                              Reply from 74.125.155.103: bytes=32 time=14ms TTL=53
                              Ping statistics for 74.125.155.103:
                              Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
                              Approximate round trip times in milli-seconds:
                              Minimum = 14ms, Maximum = 15ms, Average = 14ms
                              M:\Documents and Settings\cbadmin>ping 10.100.10.101
                              Pinging 10.100.10.101 with 32 bytes of data:
                              Request timed out.
                              Request timed out.
                              Request timed out.
                              Request timed out.
                              Ping statistics for 10.100.10.101:
                              Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
                              Approximate round trip times in milli-seconds:
                              Minimum = 0ms, Maximum = 0ms, Average = 0ms
                              M:\Documents and Settings\cbadmin>

                              Thanks,

                              Comment

                              Working...
                              X