Results 1 to 4 of 4

Thread: Can Not gain Access to IP

  1. #1
    Junior Member
    Join Date
    May 2006
    Posts
    1

    Angry Can Not gain Access to IP

    I'm a web host, I lease a server from a company.

    I have been for several years. Yesterday I ran

    into a problem. Now I have 2 accounts with the

    company. I can connect to one account but not the

    other. By account I mean our web host manager, on

    the servers. Yesterday morning I was updating

    some pages on one of the websites that I

    maintain, when I kept getting errors from the

    server that the website could not be found and

    since that point in time I have lost all

    capabilities to conect to 25 different websites

    and my web host manager.

    Now when I do a ping to the server IP's assigned

    to us. (72.232.72.2 and 72.232.72.10) the

    72.232.72.10 I get excelant results from the

    packets with a 0% Loss, but with the 72.232.72.2

    account I get 100% packet loss. I called my

    internet provider (CableLynx) and asked it there

    was anyway that the IP 72.232.72.2 had gotten a

    block on it. THier tech said noway do they block

    IP addresses. They also did a ping test on the

    72.232.72.2 IP with the results of a 60% Packet

    Loss. Now my partner, from his computer is able

    to connect to the websites on the 72.232.72.2 IP,

    but however he can not connect to the web host

    manager. I have 6 different computers in my home

    and none of the computers on my network can

    connect to 72.232.72.2 IP. 5 computers runing Win

    XP Pro, 1 running Win 98. None can connect to

    72.232.72.2, I have rest the router to default

    setting, turned eveything off and unpluged the

    power supplys for an hour. Then tried to connect

    to 72.232.72.2 with still no connection

    capabilities to that IP address. The company that

    we lease from says that they went to

    www.dnsstuff.com and did a ping test, and got

    excelant results for 72.232.72.2, I also went

    there and got excelant results from a ping test

    on 72.232.72.2 In my 12 years of working on

    computers and networking I have never ran across

    a problem like this, where a computer can connect

    to any IP address on the internet, but one (1)

    72.232.72.2. I figure that its got to be

    something in my system, possibly the router thats

    causeing the problem.

    Is there anyone that can give me some area's that

    I need to check that I have missed that would

    cause or prevent my systems from connecting to 1

    specific IP address?

  2. #2
    SG Enthusiast FunK's Avatar
    Join Date
    Aug 2000
    Posts
    2,721
    Perform traceroutes to each IP and place the results here.
    If your friend can connect and you can't it may be an issue with your packets timing out.. Traceroute will tell you how far toward the host you can actually get.

    If your providers techs are getting 60% packet loss to the .2 address, that is NOT GOOD and they should be doing something about it. Chances are you're much farther away than they are.. They should definitely have 100% to their own server.
    Simply run adaware, spybot, ZoneAlarm, HijackThis, AVG, update windows daily, have a router, don't open e-mail, turn off action scripting, don't use P2P networks, don't violate EULAs, and wear a condom to get Windows secured.

    People say Linux is alot of work!

  3. #3
    SG Enthusiast FunK's Avatar
    Join Date
    Aug 2000
    Posts
    2,721
    I can reach it

    Code:
    noles@funk:~$ ping 72.232.72.2
    PING 72.232.72.2 (72.232.72.2) 56(84) bytes of data.
    64 bytes from 72.232.72.2: icmp_seq=1 ttl=45 time=51.4 ms
    64 bytes from 72.232.72.2: icmp_seq=2 ttl=45 time=52.0 ms
    64 bytes from 72.232.72.2: icmp_seq=3 ttl=45 time=52.4 ms
    64 bytes from 72.232.72.2: icmp_seq=4 ttl=45 time=53.6 ms
    64 bytes from 72.232.72.2: icmp_seq=5 ttl=45 time=54.1 ms
    64 bytes from 72.232.72.2: icmp_seq=6 ttl=45 time=53.4 ms
    
    --- 72.232.72.2 ping statistics ---
    6 packets transmitted, 6 received, 0% packet loss, time 5003ms
    rtt min/avg/max/mdev = 51.487/52.872/54.147/0.959 ms
    noles@funk:~$ traceroute 72.232.72.2
    traceroute to 72.232.72.2 (72.232.72.2), 30 hops max, 38 byte packets
     1  cpe-066-026-050-248.nc.res.rr.com (66.26.50.248)  1.579 ms  1.589 ms  1.508  ms
     2  10.47.160.1 (10.47.160.1)  11.493 ms  11.475 ms  6.856 ms
     3  pos1-0.rlghnck-rtr1.nc.rr.com (24.25.1.113)  11.827 ms  7.887 ms  8.098 ms
     4  srp5-0.rlghncg-rtr1.nc.rr.com (24.25.2.148)  11.613 ms  8.115 ms  8.033 ms
     5  pos1-0.rlghnca-rtr1.nc.rr.com (24.25.20.17)  10.869 ms  8.946 ms  9.670 ms
     6  pos14-0.rlghncrdc-rtr1.nc.rr.com (24.25.0.5)  11.832 ms  8.645 ms  9.941 ms
     7  son1-0-1.rlghncrdc-rtr3.nc.rr.com (24.93.64.9)  11.390 ms  9.145 ms  8.042 ms
     8  67.29.172.9 (67.29.172.9)  18.228 ms 67.29.172.5 (67.29.172.5)  16.725 ms 6 7.29.172.9 (67.29.172.9)  18.143 ms
     9  ae-14-53.car4.Washington1.Level3.net (4.68.121.81)  19.045 ms ae-24-56.car4 .Washington1.Level3.net (4.68.121.177)  27.386 ms ae-14-51.car4.Washington1.Lev el3.net (4.68.121.17)  17.336 ms
    10  cpr1-ge-11-0.virginiaequinix.savvis.net (208.173.52.73)  15.960 ms cpr1-ge- 11-2.virginiaequinix.savvis.net (208.173.10.161)  16.999 ms cpr1-ge-11-0.virgin iaequinix.savvis.net (208.173.52.73)  18.371 ms
    11  bcs2-so-5-3-0.washington.savvis.net (206.24.227.45)  16.756 ms  17.269 ms 15.903 ms
    12  dcr2-so-7-3-0.Atlanta.savvis.net (204.70.192.65)  32.494 ms  33.337 ms  32. 067 ms
    13  dcr2-so-2-0-0.dallas.savvis.net (204.70.192.70)  51.073 ms  64.804 ms  50.7 61 ms
    14  bhr1-pos-1-0.fortworthda1.savvis.net (208.172.129.230)  52.993 ms  50.844 m s dcr1-so-6-0-0.dallas.savvis.net (204.70.192.49)  52.106 ms
    15  bhr1-pos-12-0.fortworthda1.savvis.net (208.172.131.82)  52.950 ms  52.004 m s  52.544 ms
    16  216.39.66.30 (216.39.66.30)  51.768 ms 216.39.64.2 (216.39.64.2)  53.036 ms   52.684 ms
    17  216.39.66.30 (216.39.66.30)  52.408 ms * 10.1.6.30 (10.1.6.30)  51.559 ms
    18  * * *
    19  * * *

    Traces are timing out though..
    I get the exact same results to the .10 address. Is your issue still happening att??

    If not, it's likely that the issue was with your provider.
    Simply run adaware, spybot, ZoneAlarm, HijackThis, AVG, update windows daily, have a router, don't open e-mail, turn off action scripting, don't use P2P networks, don't violate EULAs, and wear a condom to get Windows secured.

    People say Linux is alot of work!

  4. #4
    Elite Member TonyT's Avatar
    Join Date
    Jan 2000
    Location
    Fairfax, VA
    Posts
    10,339
    Code:
    Pinging 72.232.72.2 with 32 bytes of data:
    
    Reply from 72.232.72.2: bytes=32 time=98ms TTL=48
    Reply from 72.232.72.2: bytes=32 time=43ms TTL=48
    Reply from 72.232.72.2: bytes=32 time=43ms TTL=48
    Reply from 72.232.72.2: bytes=32 time=43ms TTL=48
    
    Ping statistics for 72.232.72.2:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 43ms, Maximum = 98ms, Average = 56ms
    
    C:\Documents and Settings\Tony>tracert 72.232.72.2
    
    Tracing route to vegas.dnsdc.com [72.232.72.2]
    over a maximum of 30 hops:
    
      1    10 ms     8 ms     9 ms  ip68-100-232-1.dc.dc.cox.net [68.100.232.1]
      2     9 ms     8 ms     8 ms  mrfdaggc01.dc.dc.cox.net [68.100.1.65]
      3     9 ms    10 ms     9 ms  ip68-100-0-1.dc.dc.cox.net [68.100.0.1]
      4     8 ms     9 ms     9 ms  mrfddsrj02gex070002.rd.dc.cox.net [68.100.0.145]
      5    12 ms     7 ms     7 ms  mrfddsrj01-so010.rd.dc.cox.net [68.100.0.129]
      6    10 ms     8 ms     9 ms  so-6-0-0.gar2.Washington1.Level3.net [67.29.170.1]
      7     9 ms     9 ms    11 ms  ae-14-55.car4.Washington1.Level3.net [4.68.121.145]
      8     9 ms     9 ms    10 ms  cpr1-ge-11-0.virginiaequinix.savvis.net [208.173.52.73]
      9    12 ms    11 ms    12 ms  bcs1-so-0-0-0.Washington.savvis.net [208.173.52.114]
     10    13 ms    26 ms    25 ms  dcr1-so-3-0-0.Atlanta.savvis.net [204.70.192.53]
     11    26 ms    50 ms    22 ms  dcr2-so-7-2-0.Atlanta.savvis.net [204.70.192.57]
     12    44 ms    46 ms    45 ms  dcr2-so-2-0-0.dallas.savvis.net [204.70.192.70]
     13   274 ms    45 ms    47 ms  bhr2-pos-4-0.fortworthda1.savvis.net [208.172.131.86]
     14    47 ms    45 ms    45 ms  216.39.64.27
     15     *       44 ms     *     216.39.66.30
     16     *        *        *     Request timed out.
     17    44 ms    43 ms     *     vegas.dnsdc.com [72.232.72.2]
     18    44 ms    44 ms    44 ms  vegas.dnsdc.com [72.232.72.2]
    
    Trace complete.
    
    C:\Documents and Settings\Tony>ping 72.232.72.10
    
    Pinging 72.232.72.10 with 32 bytes of data:
    
    Reply from 72.232.72.10: bytes=32 time=46ms TTL=48
    Reply from 72.232.72.10: bytes=32 time=44ms TTL=48
    Reply from 72.232.72.10: bytes=32 time=46ms TTL=48
    Reply from 72.232.72.10: bytes=32 time=43ms TTL=48
    
    Ping statistics for 72.232.72.10:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 43ms, Maximum = 46ms, Average = 44ms
    
    C:\Documents and Settings\Tony>tracert 72.232.72.10
    
    Tracing route to montreal.dnsdc7.com [72.232.72.10]
    over a maximum of 30 hops:
    
      1     *        7 ms     9 ms  ip68-100-232-1.dc.dc.cox.net [68.100.232.1]
      2     9 ms     9 ms     9 ms  mrfdaggc01.dc.dc.cox.net [68.100.1.65]
      3     9 ms     9 ms     7 ms  ip68-100-0-1.dc.dc.cox.net [68.100.0.1]
      4    23 ms    14 ms    20 ms  mrfddsrj01gex070004.rd.dc.cox.net [68.100.0.161]
      5     7 ms     9 ms     9 ms  so-6-0-0.gar2.Washington1.Level3.net [67.29.170.1]
      6    11 ms    10 ms     8 ms  ae-24-56.car4.Washington1.Level3.net [4.68.121.177]
      7    13 ms     7 ms     9 ms  cpr1-ge-11-0.virginiaequinix.savvis.net [208.173.52.73]
      8    11 ms    10 ms    17 ms  bcs1-so-3-3-0.Washington.savvis.net [206.24.238.97]
      9    24 ms    12 ms    25 ms  dcr1-so-3-0-0.Atlanta.savvis.net [204.70.192.53]
     10    43 ms    24 ms    45 ms  dcr1-so-3-2-0.dallas.savvis.net [204.70.192.82]
     11    48 ms    43 ms    46 ms  bhr1-pos-12-0.fortworthda1.savvis.net [208.172.131.82]
     12    45 ms    47 ms    43 ms  csr1-ve240.fortworthda1.savvis.net [216.39.64.34]
     13    45 ms    45 ms    44 ms  csr1-ve240.fortworthda1.savvis.net [216.39.64.34]
     14     *        *       43 ms  216.39.79.214
     15     *        *        *     Request timed out.
     16     *        *        *     Request timed out.
     17    47 ms     *       46 ms  montreal.dnsdc7.com [72.232.72.10]
    
    Trace complete.
    Code:
    Starting nmap 3.93 ( http://www.insecure.org/nmap ) at 2006-05-22 18:13 Eastern Standard
    Initiating SYN Stealth Scan against vegas.dnsdc.com (72.232.72.2) [1668 ports] at 18:13
    Discovered open port 53/tcp on 72.232.72.2
    Discovered open port 80/tcp on 72.232.72.2
    Discovered open port 443/tcp on 72.232.72.2
    Discovered open port 21/tcp on 72.232.72.2
    Discovered open port 22/tcp on 72.232.72.2
    Discovered open port 3306/tcp on 72.232.72.2
    Discovered open port 26/tcp on 72.232.72.2
    Discovered open port 143/tcp on 72.232.72.2
    Discovered open port 110/tcp on 72.232.72.2
    The SYN Stealth Scan took 15.91s to scan 1668 total ports.
    For OSScan assuming port 21 is open, 43 is closed, and neither are firewalled
    Host vegas.dnsdc.com (72.232.72.2) appears to be up ... good.
    Interesting ports on vegas.dnsdc.com (72.232.72.2):
    (The 1643 ports scanned but not shown below are in state: filtered)
    PORT      STATE  SERVICE
    21/tcp    open   ftp
    22/tcp    open   ssh
    26/tcp    open   unknown
    43/tcp    closed whois
    53/tcp    open   domain
    80/tcp    open   http
    110/tcp   open   pop3
    143/tcp   open   imap
    443/tcp   open   https
    873/tcp   closed rsync
    3306/tcp  open   mysql
    31337/tcp closed Elite
    32770/tcp closed sometimes-rpc3
    32771/tcp closed sometimes-rpc5
    32772/tcp closed sometimes-rpc7
    32773/tcp closed sometimes-rpc9
    32774/tcp closed sometimes-rpc11
    32775/tcp closed sometimes-rpc13
    32776/tcp closed sometimes-rpc15
    32777/tcp closed sometimes-rpc17
    32778/tcp closed sometimes-rpc19
    32779/tcp closed sometimes-rpc21
    32780/tcp closed sometimes-rpc23
    32786/tcp closed sometimes-rpc25
    32787/tcp closed sometimes-rpc27
    Device type: general purpose
    Running: Linux 2.4.X|2.6.X
    OS details: Linux 2.4.20 - 2.4.22, Linux 2.6.10 - 2.6.11
    TCP Sequence Prediction: Class=random positive increments
                             Difficulty=5103454 (Good luck!)
    IPID Sequence Generation: All zeros
    
    Nmap finished: 1 IP address (1 host up) scanned in 18.719 seconds
                   Raw packets sent: 3336 (135KB) | Rcvd: 36 (1656B)
    No one has any right to force data on you
    and command you to believe it or else.
    If it is not true for you, it isn't true.

    LRH

Similar Threads

  1. WAP54G Web Configuration access woes
    By MadMattUK in forum Wireless Networks & Routers
    Replies: 6
    Last Post: 06-09-08, 04:31 PM
  2. Access point speed which support a and b
    By clement_3117 in forum Wireless Networks & Routers
    Replies: 3
    Last Post: 12-13-05, 05:07 AM
  3. Replies: 2
    Last Post: 11-19-05, 12:27 PM
  4. Web access or router access not both???
    By berrybry in forum Networking Forum
    Replies: 5
    Last Post: 10-03-05, 10:01 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •