1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Unable to access 192.xxx.xxx.xxx Website through router

Discussion in 'Networking (Hardware & Software)' started by Daanii, 2007/02/27.

  1. 2007/02/28
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,068
    Likes Received:
    396
    If you can get Internet via the router, open a cmd window and do:
    ping 192.150.18.60
    to see if your isp dns servers are working for that address.
    If no joy, you can add a secondary dns server manually for your local area connection tcp/ip properties, but use a dns server other than your isp dns server, such as one available here:
    http://80.247.230.136/dns.htm
     
    Last edited: 2007/02/28
  2. 2007/02/28
    Daanii

    Daanii Well-Known Member Thread Starter

    Joined:
    2002/04/04
    Messages:
    341
    Likes Received:
    2
    Using the command line to ping 192.168.18.60 does work. That has always worked.
     

  3. to hide this advert.

  4. 2007/02/28
    Daanii

    Daanii Well-Known Member Thread Starter

    Joined:
    2002/04/04
    Messages:
    341
    Likes Received:
    2
    I saw somewhere a suggestion to change my MTU, which is currently at 1440. Should I try that?
     
  5. 2007/03/01
    Dytrog

    Dytrog Inactive

    Joined:
    2007/01/13
    Messages:
    341
    Likes Received:
    0
  6. 2007/03/01
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,068
    Likes Received:
    396
    No, ping the adobe ip address. 192.150.18.60
    If you have adsl internet, then yes, set mtu in router to 1492, if cable internet then no need to change mtu.
     
  7. 2007/03/01
    Daanii

    Daanii Well-Known Member Thread Starter

    Joined:
    2002/04/04
    Messages:
    341
    Likes Received:
    2
    Sorry, I mistyped the address. A ping to 192.150.18.60 works.

    I think I changed the MTU correctly, using the Dr. TCP program. But still no luck in connecting to www.adobe.com.
     
  8. 2007/03/01
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,068
    Likes Received:
    396
    If have dsl connection you have to access the router control panel via browser ( 192.168.0.1 ) and change the MTU there, not on your comp using Dr. TCP.

    try to clear the xp dns cache:
    ipconfig /flushdns
    for more ipconfig options type: (lots of dns tricks there)
    ipconfig --h

    you can also t-shoot using nslookup:
    nslookup 192.150.18.60

    netsh is also a great net t-shooting tool built into windows:
    http://commandwindows.com/netsh.htm
     
  9. 2007/03/01
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    What do you get if you enter this at the command line:

    nslookup www.adobe.com

    Even better enter this:

    nslookup www.adobe.com > nslookup.txt

    That will create a file called nslookup.txt. Post the contents of that file here.
     
  10. 2007/03/01
    Daanii

    Daanii Well-Known Member Thread Starter

    Joined:
    2002/04/04
    Messages:
    341
    Likes Received:
    2
  11. 2007/03/01
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    So name resolution is working and you say you can ping the IP 192.150.18.60.

    I think this means this is not a network problem. One last test should confirm that. Enter this at a command prompt:
    Code:
    telnet 192.150.18.60 80
    There is a space between the IP address and the 80 (which tells telnet to use port 80). What you should get is a blank screen. If you then type:
    Code:
    get index.html
    You won't be able to see what you type but on hitting return, your console screen should be filled with a load of html code.

    If that works we need to be looking for a problem on your PC. Most probably a browser problem (cache for example). I'd suggest that a next step might be to try another browser. If you can connect with a different browser, that fairly well confirms that it is your current browser that is the problem (either a setting, a config, or a bug). If you cannot connect with a different browser, I'd look for incorrect proxy settings and firewall settings.

    It also means that the host file entry is redundant. I'd remove the line you added.
     
  12. 2007/03/01
    Daanii

    Daanii Well-Known Member Thread Starter

    Joined:
    2002/04/04
    Messages:
    341
    Likes Received:
    2
    When I type in telnet 192.150.18.60 80 at the command prompt, I get the following immediately:

    Connecting to 192.150.18.60...

    then after about 20 seconds, I get

    Could not open connection to the host, on port 80: Connect failed
     
  13. 2007/03/01
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    Well that puts the cat amongst the pigeons as my mum would say. What is your make and model of router and/or modem? Also, have you discussed this problem with your ISP?
     
  14. 2007/03/01
    Daanii

    Daanii Well-Known Member Thread Starter

    Joined:
    2002/04/04
    Messages:
    341
    Likes Received:
    2
    My router is a Netgear MR814. The DSL modem is a SpeadStream 5100.

    I might also mention that I have three computers attached by wire to the router, and one attached by wireless. None of them can access www.adobe.com now using either Internet Explorer or Mozilla Firefox. To access www.adobe.com, I have to use dialup.

    I have tried to connect directly to my ISP through the modem without using the router, to see if I can access www.adobe.com that way. But I have been unable to get that to work. I'm afraid that shows how limited my networking knowledge is.
     
  15. 2007/03/01
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    OK - lets look at filtering problems at the router. If you don't have it already, you can download a copy of the manual for the router from Netgear. The section that catches my eye is chapter 6 "Content Filtering ". This could be where the problem lies. On page 6-2 there is a description of how to access the filtering logs. So next step is to check that and see if the logs show a block.

    Have a look at section "Block Sites" on page 6-3. That shows you where block sites will be set up. You probably need to remove any settings you find there.

    On page 6-5 there is a section on filtering services by IP address. Again check those settings on your router.
     
  16. 2007/03/01
    Daanii

    Daanii Well-Known Member Thread Starter

    Joined:
    2002/04/04
    Messages:
    341
    Likes Received:
    2
    The filtering does not seem to be a problem. All filtering is off. I have never tried to do anything with it.

    I should also mention that this problem came up only about a year ago. Prior to that I was able to access www.adobe.com.

    What sticks in my mind is the fact that I was able once to access the site after I changed the hosts file. Or maybe it was switching the network settings, which I did at the same time. When the Adobe site came up, it came up rather slowly. Don't know if that has anything to do with anything.

    Since that one time, it has not worked again.
     
  17. 2007/03/01
    Daanii

    Daanii Well-Known Member Thread Starter

    Joined:
    2002/04/04
    Messages:
    341
    Likes Received:
    2
    Reading my post, I neglected to mention that I did check the Netgear manual you referred to, and checked the filters on the Netgear router admin pages. No filtering showed up. Which is consistent with my never having touched that before.
     
  18. 2007/03/01
    Daanii

    Daanii Well-Known Member Thread Starter

    Joined:
    2002/04/04
    Messages:
    341
    Likes Received:
    2
    A couple more notes.

    Netscape also times out when I try to access www.adobe.com. So I've tried Firefox, Internet Explorer, and Netscape, and get the same result with all.

    But I just noticed another site that does not work with Firefox. That is www.vonage.com. It also times out, just like www.adobe.com. But in Internet Explorer and Netscape, www.vonage.com works fine.
     
  19. 2007/03/01
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,068
    Likes Received:
    396
    Who is your isp?
    What are their DNS server ip addresses? Post them here.
    And have a look at the Windows Firewall. You may have at one time blocked the Acrobat Reader Auto Update program and as a result *.adobe.com is filtered.
     
  20. 2007/03/01
    Daanii

    Daanii Well-Known Member Thread Starter

    Joined:
    2002/04/04
    Messages:
    341
    Likes Received:
    2
    ISP is sbcglobal.net.

    DNS servers are:
    68.94.156.1
    68.94.157.1

    Sorry I missed an earlier post from you, TonyT. You noted that I need to set the MTU in the router. I cannot find any way to do that.

    Thanks for the other suggestions you had, too. I'll look at the various options in netsh and try a few more things. What I have tried so far has not really shown up any problems.
     
  21. 2007/03/02
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    BTW, the reason that I think you should check with your ISP is that it is common and good practice for ISPs to block all private IP address. So ISPs will usually block traffic sent to or from 192.168.x.x and 10.x.x.x addresses. It is possible that your ISP has got this block miss-configured and is blocking all 192 addresses. It may well not be the cause of the problem, but is worth ruling out.
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.