We help IT Professionals succeed at work.

Access blocked to a vendors servers on internet

Cdwalter
Cdwalter used Ask the Experts™
on
I have a network in my home office with cisco 1811 router and Windows 7 laptop, Windows XP desktop, Windows Vista desktop and Windows 2003 server. My web site and email are hosted by a thrid party. About a week ago my server no longer can access the hosting companies servers. I can not get pop connection, odbc connection or browse my web site from the server. This server can access any other sites such as google, yahoo, cnn etc. I have no issues from any of my other PCs on the network. Here is what I have tried so far. There are least 3 differnet IP addresses that I am unable to access.
1 Cleared routing table
2 Disables second nic
3 Disables local DNS
4 Removed static IP address
5. Disabled firewall
6. Ping host gets = dest host unreachable, can ping other sites

I noticed this when my ODBC connection stopped working .
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Bryon HSenior Technical Support Analyst
Top Expert 2010

Commented:
all the workstations that can access your web host, and the server that cannot access your web host - do they all have the same outside ip address?  you can go to www.cmyip.com from each machine to verify

when pinging, what ip address reports destination unreachable?

what about this:
pathping ip.of.host.net
(obviously the ip address of your host goes there)

lets see where it stops

the server that cannot reach the host - is it its own dns server?  do you have a forward lookup zone in dns for yourdomain.com?  probably you do and the "A" record for www (or others) is now outdated as your host maybe changed their ip address.  your local dns forward lookup zone won't auto-update itself.

CdwalterOwner

Author

Commented:
One Time Warner internet connection, all PCs report same IP from cmyip.com3  
192.168.5.1 is my router\gateway. The sever does have local DNS but the current TCPIP connections are not configured to look at it the Time Warner DNS 209.18.47.61 an 62 are hard coded.

Pathping from server
Tracing route to router.iweb45.net [216.249.102.108]
over a maximum of 30 hops:
  0  porthos.Castlecomputing.net [192.168.5.19]
  1  Destination host unreachable.
Computing statistics for 25 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           porthos.Castlecomputing.net [192.168.5.19]
                              100/ 100 =100%   |
  1  ---     100/ 100 =100%     0/ 100 =  0%  porthos.Castlecomputing.net [0.0.0.0]
Trace complete.

From laptop on same network
C:\>pathping 216.249.102.108

Tracing route to 216.249.102.108 over a maximum of 30 hops

  0  Arimas.carolina.rr.com [192.168.5.128]
  1  192.168.5.1
  2  10.217.128.1
  3  24.93.75.1
  4  srp8-0.chrlncsa-rtr1.carolina.rr.com [24.93.70.193]
  5  ge-2-2-0.rlghncrdc-pop1.southeast.rr.com [24.93.64.171]
  6  ae-3-0.cr0.dca10.tbone.rr.com [66.109.6.80]
  7  ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
  8  64.132.69.61
  9  hagg-03-ge-1-0-0-538.chrl.twtelecom.net [66.192.242.241]
 10  CCC.CHLT.R002.CharlotteColo.com [216.249.96.4]
 11  22.static.gw.INet45.com [209.136.192.22]
 12     *        *        *
Computing statistics for 275 seconds...
CdwalterOwner

Author

Commented:
Current IP Config from Server
Windows IP Configuration

   Host Name . . . . . . . . . . . . : porthos
   Primary Dns Suffix  . . . . . . . : Castlecomputing.net
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : Yes
   DNS Suffix Search List. . . . . . : Castlecomputing.net

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controller
   Physical Address. . . . . . . . . : 00-1D-09-0A-A9-6A
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.5.16
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.5.1
   DNS Servers . . . . . . . . . . . : 209.18.47.62
                                       209.18.47.61

Ethernet adapter Local Area Connection SQL:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : IBM Netfinity 10/100 Ethernet Adapter
   Physical Address. . . . . . . . . : 00-04-AC-58-D9-D0
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.5.19
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 209.18.47.61
                                       209.18.47.62
Bryon HSenior Technical Support Analyst
Top Expert 2010

Commented:
ok so it's trying to route out your nic called "192.168.5.19 / lan SQL"  which doesn't have a gateway

what is the purpose of that nic?  what does it connect to?

is it possible to perm-disable that nic?  you'll need a reboot after disabling it.

or - you can assign it a gateway and everything will work fine.

note that if you have any kind of domain running, it's totally broken because your dns is external on the nics of the server and workstations, expect a 5-10 minute delay logging in, and inability to access server resources.

the right way is to have the server and all workstations hard coded to the dns of your internal server, and have your internal DNS having a forwarder being time warners dns servers.  but, this isn't affecting your ability to contact the external host - not having a gateway on the second nic is
CdwalterOwner

Author

Commented:
Some of the screwy setting are due to tring to trouble shoot this problem. Everything had been working for over a year until last week. The Hosting companies IP did not change. I have disabled the second nic 192.168.5.19 (SQL) and rebooted --- same problem. The gateway on the second nic was removed today to get rid of an multi gateway error on the config screen.The second nic is no longer needed and can be perm disabled.
Bryon HSenior Technical Support Analyst
Top Expert 2010

Commented:
ok so with the second nic disabled, and a reboot, lets see a pathping from that

as long as you're in dos, fire it one of these:
route print

CdwalterOwner

Author

Commented:
Also remember I'm have no problem accessing anything else from this server google, yhaoo, weather.com etc..... just the three IP address and it does not matter if I use IP address or name I get same results so I don't think its DNS related. something on the server seems to beblocking or dropping traffic to these 3 ip addresses
CdwalterOwner

Author

Commented:
Pathping and route print

Tracing route to router.iweb45.net [216.249.102.108]
over a maximum of 30 hops:
  0  porthos.Castlecomputing.net [192.168.5.16]
  1  Destination host unreachable.
Computing statistics for 25 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           porthos.Castlecomputing.net [192.168.5.16]         100/ 100 =100%   |
  1  ---     100/ 100 =100%     0/ 100 =  0%  porthos.Castlecomputing.net [0.0.0.0]
Trace complete.

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 1d 09 0a a9 6a ...... Broadcom NetXtreme 57xx Gigabit Controller
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.5.1     192.168.5.16     20
       24.25.26.0    255.255.255.0     192.168.5.17         ffffffff      1
      38.103.37.0    255.255.255.0     192.168.5.17         ffffffff      1
      38.117.98.0    255.255.255.0     192.168.5.17         ffffffff      1
      58.83.135.0    255.255.255.0     192.168.5.17         ffffffff      1
      58.221.42.0    255.255.255.0     192.168.5.17         ffffffff      1
       59.54.54.0    255.255.255.0     192.168.5.17         ffffffff      1
      60.18.150.0    255.255.255.0     192.168.5.17         ffffffff      1
      60.28.200.0    255.255.255.0     192.168.5.17         ffffffff      1
      60.28.216.0    255.255.255.0     192.168.5.17         ffffffff      1
     60.190.222.0    255.255.255.0     192.168.5.17         ffffffff      1
      61.18.146.0    255.255.255.0     192.168.5.17         ffffffff      1
      61.129.59.0    255.255.255.0     192.168.5.17         ffffffff      1
     61.133.127.0    255.255.255.0     192.168.5.17         ffffffff      1
     61.147.110.0    255.255.255.0     192.168.5.17         ffffffff      1
      61.181.17.0    255.255.255.0     192.168.5.17         ffffffff      1
      62.67.184.0    255.255.255.0     192.168.5.17         ffffffff      1
      64.74.243.0    255.255.255.0     192.168.5.17         ffffffff      1
     68.142.118.0    255.255.255.0     192.168.5.17         ffffffff      1
     80.239.156.0    255.255.255.0     192.168.5.17         ffffffff      1
     80.239.197.0    255.255.255.0     192.168.5.17         ffffffff      1
       82.129.8.0    255.255.255.0     192.168.5.17         ffffffff      1
       85.12.30.0    255.255.255.0     192.168.5.17         ffffffff      1
     89.202.149.0    255.255.255.0     192.168.5.17         ffffffff      1
     89.202.157.0    255.255.255.0     192.168.5.17         ffffffff      1
     90.183.101.0    255.255.255.0     192.168.5.17         ffffffff      1
      93.184.71.0    255.255.255.0     192.168.5.17         ffffffff      1
     110.81.238.0    255.255.255.0     192.168.5.17         ffffffff      1
     110.81.239.0    255.255.255.0     192.168.5.17         ffffffff      1
    110.232.176.0    255.255.255.0     192.168.5.17         ffffffff      1
    113.106.201.0    255.255.255.0     192.168.5.17         ffffffff      1
    117.135.135.0    255.255.255.0     192.168.5.17         ffffffff      1
    117.135.144.0    255.255.255.0     192.168.5.17         ffffffff      1
    118.119.189.0    255.255.255.0     192.168.5.17         ffffffff      1
      119.188.2.0    255.255.255.0     192.168.5.17         ffffffff      1
      121.14.11.0    255.255.255.0     192.168.5.17         ffffffff      1
     121.14.158.0    255.255.255.0     192.168.5.17         ffffffff      1
    121.101.223.0    255.255.255.0     192.168.5.17         ffffffff      1
    122.226.213.0    255.255.255.0     192.168.5.17         ffffffff      1
     123.235.37.0    255.255.255.0     192.168.5.17         ffffffff      1
    124.131.220.0    255.255.255.0     192.168.5.17         ffffffff      1
    124.238.243.0    255.255.255.0     192.168.5.17         ffffffff      1
    124.238.244.0    255.255.255.0     192.168.5.17         ffffffff      1
    124.238.254.0    255.255.255.0     192.168.5.17         ffffffff      1
      125.39.61.0    255.255.255.0     192.168.5.17         ffffffff      1
     125.39.100.0    255.255.255.0     192.168.5.17         ffffffff      1
       125.46.1.0    255.255.255.0     192.168.5.17         ffffffff      1
      125.46.58.0    255.255.255.0     192.168.5.17         ffffffff      1
        127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1      1
      169.254.0.0      255.255.0.0     192.168.5.16     192.168.5.16     30
      192.168.5.0    255.255.255.0     192.168.5.16     192.168.5.16     20
     192.168.5.16  255.255.255.255        127.0.0.1        127.0.0.1     20
    192.168.5.255  255.255.255.255     192.168.5.16     192.168.5.16     20
    193.138.220.0    255.255.255.0     192.168.5.17         ffffffff      1
     195.222.17.0    255.255.255.0     192.168.5.17         ffffffff      1
    208.111.160.0    255.255.255.0     192.168.5.17         ffffffff      1
    208.111.161.0    255.255.255.0     192.168.5.17         ffffffff      1
    208.111.182.0    255.255.255.0     192.168.5.17         ffffffff      1
    211.103.159.0    255.255.255.0     192.168.5.17         ffffffff      1
     212.47.219.0    255.255.255.0     192.168.5.17         ffffffff      1
     212.96.161.0    255.255.255.0     192.168.5.17         ffffffff      1
    216.249.102.0    255.255.255.0     192.168.5.17         ffffffff      1
       218.6.12.0    255.255.255.0     192.168.5.17         ffffffff      1
      218.30.82.0    255.255.255.0     192.168.5.17         ffffffff      1
      218.56.43.0    255.255.255.0     192.168.5.17         ffffffff      1
      218.60.47.0    255.255.255.0     192.168.5.17         ffffffff      1
      218.93.16.0    255.255.255.0     192.168.5.17         ffffffff      1
    219.138.163.0    255.255.255.0     192.168.5.17         ffffffff      1
    219.232.254.0    255.255.255.0     192.168.5.17         ffffffff      1
     219.238.45.0    255.255.255.0     192.168.5.17         ffffffff      1
    219.238.233.0    255.255.255.0     192.168.5.17         ffffffff      1
     220.181.85.0    255.255.255.0     192.168.5.17         ffffffff      1
    220.181.126.0    255.255.255.0     192.168.5.17         ffffffff      1
    221.192.148.0    255.255.255.0     192.168.5.17         ffffffff      1
    221.192.151.0    255.255.255.0     192.168.5.17         ffffffff      1
    221.194.142.0    255.255.255.0     192.168.5.17         ffffffff      1
    222.135.144.0    255.255.255.0     192.168.5.17         ffffffff      1
    222.186.189.0    255.255.255.0     192.168.5.17         ffffffff      1
    222.242.199.0    255.255.255.0     192.168.5.17         ffffffff      1
        224.0.0.0        240.0.0.0     192.168.5.16     192.168.5.16     20
  255.255.255.255  255.255.255.255     192.168.5.16     192.168.5.16      1
Default Gateway:       192.168.5.1
===========================================================================
Persistent Routes:
  None
CdwalterOwner

Author

Commented:
I cleared routing table and I'm rebooting to rebuild. at one point I had 3 IP address on the main nic 16,17,18 I will resend the routing table after reboot
Bryon HSenior Technical Support Analyst
Top Expert 2010

Commented:
yeah here's the problem:
216.249.102.0    255.255.255.0     192.168.5.17

it's trying to contact your nic at 5.17, whereas your nic is 5.16... that's why it cannot route out

that routing table needs to be cleared... curious to see what happens after you're doing that

anything that has 5.17 in the 3rd column there, you can't get to.  the server really really thinks its ip address is 5.17, but the nic is set for 5.16.
CdwalterOwner

Author

Commented:
Interesting ... I did route -f then route print the route table was cleared. I rebooted then did route print 192.168.5.17 routings are back in the table I checked Nic settings and it only has IP 192.168.5.16
CdwalterOwner

Author

Commented:
Current routing table after reboot
IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 1d 09 0a a9 6a ...... Broadcom NetXtreme 57xx Gigabit Controller
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.5.1     192.168.5.16     20
       24.25.26.0    255.255.255.0     192.168.5.17         ffffffff      1
      38.103.37.0    255.255.255.0     192.168.5.17         ffffffff      1
      38.117.98.0    255.255.255.0     192.168.5.17         ffffffff      1
      58.83.135.0    255.255.255.0     192.168.5.17         ffffffff      1
      58.221.42.0    255.255.255.0     192.168.5.17         ffffffff      1
       59.54.54.0    255.255.255.0     192.168.5.17         ffffffff      1
      60.18.146.0    255.255.255.0     192.168.5.17         ffffffff      1
      60.18.150.0    255.255.255.0     192.168.5.17         ffffffff      1
      60.28.200.0    255.255.255.0     192.168.5.17         ffffffff      1
      60.28.216.0    255.255.255.0     192.168.5.17         ffffffff      1
     60.190.222.0    255.255.255.0     192.168.5.17         ffffffff      1
      61.129.59.0    255.255.255.0     192.168.5.17         ffffffff      1
     61.133.127.0    255.255.255.0     192.168.5.17         ffffffff      1
     61.147.110.0    255.255.255.0     192.168.5.17         ffffffff      1
      61.181.17.0    255.255.255.0     192.168.5.17         ffffffff      1
      62.67.184.0    255.255.255.0     192.168.5.17         ffffffff      1
      64.74.243.0    255.255.255.0     192.168.5.17         ffffffff      1
     68.142.118.0    255.255.255.0     192.168.5.17         ffffffff      1
     80.239.156.0    255.255.255.0     192.168.5.17         ffffffff      1
     80.239.197.0    255.255.255.0     192.168.5.17         ffffffff      1
       85.12.30.0    255.255.255.0     192.168.5.17         ffffffff      1
       85.12.57.0    255.255.255.0     192.168.5.17         ffffffff      1
       85.12.58.0    255.255.255.0     192.168.5.17         ffffffff      1
       85.17.72.0    255.255.255.0     192.168.5.17         ffffffff      1
     89.202.149.0    255.255.255.0     192.168.5.17         ffffffff      1
     89.202.157.0    255.255.255.0     192.168.5.17         ffffffff      1
     90.183.101.0    255.255.255.0     192.168.5.17         ffffffff      1
      93.184.71.0    255.255.255.0     192.168.5.17         ffffffff      1
     110.81.239.0    255.255.255.0     192.168.5.17         ffffffff      1
    110.232.176.0    255.255.255.0     192.168.5.17         ffffffff      1
    113.106.201.0    255.255.255.0     192.168.5.17         ffffffff      1
    117.135.135.0    255.255.255.0     192.168.5.17         ffffffff      1
    117.135.144.0    255.255.255.0     192.168.5.17         ffffffff      1
    118.119.189.0    255.255.255.0     192.168.5.17         ffffffff      1
    118.123.112.0    255.255.255.0     192.168.5.17         ffffffff      1
      119.188.2.0    255.255.255.0     192.168.5.17         ffffffff      1
      121.14.11.0    255.255.255.0     192.168.5.17         ffffffff      1
     121.14.158.0    255.255.255.0     192.168.5.17         ffffffff      1
    121.101.223.0    255.255.255.0     192.168.5.17         ffffffff      1
    122.226.213.0    255.255.255.0     192.168.5.17         ffffffff      1
Bryon HSenior Technical Support Analyst
Top Expert 2010

Commented:
with the route -f, then ping, does it reply?

are you able to uninstall both network cards (device manager), then scan for hardware changes and let them reinstall?  (then disable or unplug the second nic)
Bryon HSenior Technical Support Analyst
Top Expert 2010

Commented:
you'll need to recode your ip info of course, after all that
Bryon HSenior Technical Support Analyst
Top Expert 2010

Commented:
on a side note, double check this:
internet explorer > tools > internet options > connections > lan settings
there should be no checkmarks unless you expect to be using a proxy server.

i'm wondering if something on the server is trying to proxy all this stuff out some other device (5.17)
CdwalterOwner

Author

Commented:
no checks under lan settings. It will be a little while before I can delete and readd the nics I have something running on the server at the moment
Bryon HSenior Technical Support Analyst
Top Expert 2010

Commented:
ok we just have to find out why the server thinks it is 5.17 after a reboot when you say it's clearly not

you could double check in the lan properties, ADVANCED, ip addresses.. you might still have a second one in there?  (or in the disabled nic, just empty out the disabled one)

worst case, you could assign a secondary ip of 5.17 to the enabled nic, as long as it has a gateway it would work
CdwalterOwner

Author

Commented:
I deleted the Nics from device manager and rescanned, disabled second nic and reset up 1st nic with 5.16 same results. I did route -f and could NOT ping 216.249.102.108
CdwalterOwner

Author

Commented:
I added 5.17 under advanced setting -- same results 5.16 and 5.17 are both set up on the 1st nic and the second nic is disabled. The route table does not appear to have changed.
Bryon HSenior Technical Support Analyst
Top Expert 2010

Commented:
can you look around or think about what software you might have installed, that would affect this?

something is telling the server to route these things out 192.168.5.17, even when 5.17 doesn't exist.  

maybe a 3rd party vpn connection, some remote access connector, anything weird in your 'my network places', weird adapters, etc?

can you go into the tcp properties of your disabled nic, and set its metric for like 20, even though it's disabled?  (or enable, do it, disable)
see if your primary nic is metric 1 or at least lower than the disabled one

are they teamed, or load balanced, or bridged?

CdwalterOwner

Author

Commented:
I'm not aware of an new software on this PC. I changed the matric settings same results
CdwalterOwner

Author

Commented:
OK this is rea weird now.
* I entered route -f, and then route print the route table was cleared
* I entered Route -p add 0.0.0.0 mask 0.0.0.0 192.168.5.1 where 5.1 is my router. I can now ping the web site and set up ODBC connection.
* about 2-3 minutes later everything stops working and I do Route Print again and the route table is back with all the entries for 5.17 and I can't access anything again.

What would make my route table reload with old entries?  
Owner
Commented:
I'm not sure what the problem was but its fixed now. I turn Routing and remote access back on, then stopped it. ran route -f and restarted RARA and it has been working for a couple hours. Before when RARA was not on the old routing table would come back.
Bryon HSenior Technical Support Analyst
Top Expert 2010

Commented:
yeah i can't think of anything that would automatically add all those routes - does it seem cleared up now after doing that process with RARA?