Link to home
Create AccountLog in
Avatar of brcarter52
brcarter52

asked on

waiting on websites

HI all,

I have been working on this problem for about a month now and am comopletely stumped.  I have a
customer that has ADSL and 6 static IP addresses.  The modem is setup to authenticate the PPPoe
username and password and has a "Public Lan" where it gives out the 3 of the IP's via DHCP, 2 IP's are
setup in sepearte routers and the other one is the IP of the DSL modem.  

Here is the setup, the dsl modem goes into a switch then a patch cable goes from the switch into my router
and a patch cable goes from the switch into another companies router.

Here is the problem.  There are alot of websites that you can get to for example, espn.com, google.com
and yahoo.com.  Some of the websites that you cannot get to are msn.com, medicare.gov and
walgreens.com.  These websites that will not load sit there and say waiting on www.medicare.gov and
will eventually time out.

Here is what I've tried to fix this issue.
1.  put new router in place-netgear fvs338
2. put new modem in place-westell g90-610014-20
3. plugged laptop direclty into modem and same issues occur.  Same laptop plugged in at my office will
go to any website I ask it to.
4. new set of static IP's in case the first one were somehow blacklisted.

The issue happens both behind the modem or the router, which has me really stumped.

Any help or suggestions would be appreciated.  I'm out of ideas.  I've spent many hours on the phone with the ISP
and they have said these websites were blocking the IP's, but with the new set of IP's it's still happening.


Thanks
Avatar of Josef Pospisil
Josef Pospisil
Flag of Germany image

Hello,

please try to type the IP Adress in the Browser intead of the URL for sites not working. Like http://ip-of-msn.com. You can determine the IP by pinging the URL in the console like ping msn.com. If this would work you could choose a public DNS instead of the ISPs DNS.
Avatar of brcarter52
brcarter52

ASKER

I have tried this and it still won't go to the website.  I have tried both the ISP's DNS#'s and OpenDNS#'s as well as google's DNS#'s

I have used the following DNS#'s
208.67.220.220
208.67.222.222
8.8.8.8
ASKER CERTIFIED SOLUTION
Avatar of Josef Pospisil
Josef Pospisil
Flag of Germany image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
http://www.broadbandreports.com/forum/r24511144-CenturyTel-Westell-G90-610014-20-Firewall-blocks-outgoing-port and other gamer forums complain about the internal firewall of the modem blocking ports, especially outgoing ports. Perhaps the one you replaced was also Westel?  I would note that the sites you say work are smaller html only pages and the sites that "waiting on www.medicare.gov" type messages are many times larger and include *.js and *.css files when I save the sites to my computer; an auxilliary file may be blocked by the firewall or it may simply time out due to the slowness of a typical DSL.  What is the other Internet (that works) connection? I have a Westel W27 wireless router set in bridge mode that works OK. Maybe I'm used to DOCSYS and Wireless but does your ISP still use PPPOE? Its a bit old.
Jelcin: I am going onsite this afternoon and will give that a shot, I will see if anything stands out to me and if it doesn't I'll post it up here.

Shjacks55:  I tried what that article said and still having the same issue.  I can do a speedtest on the DSL line and get 6MB/s down and 712 up, so I do not believe it's a typical DSL slowness issue.  Also ya know, TCP/IP is an old protocol just like PPPoE, but still used...I am just trying to help my customer with what we have to work with.
Try lowering the MTU on the internet router by 100 or 200. Then see how the websites respond.
1. ppoe=point to point protocol over ethernet
you are using a serial line protocol to log into a gateway server not the internet, but you are pretending the ethernet is a serial line. back in olden days before ethernet it was easier to interface weird connections to serial line. The phone company sends ATM packets not IP packets to your DSL Modem (MODulator-DEModulator; used to translate unrelated signal type like like analog tones to digital data) which is also a Gateway from ATM to Ethernet. (PPP predates Internet Protocol when Internet used Network Control Protocol.)
2. Ethernet by wire typically uses 1536 byte packets, Internet often fragments these to minimum size so MTU for internet connectivity should be 512 bytes which is usually set by Windows automatically. Since you are not connected directly to the Internet but to a router connected to a pretend internet protocol connected via modem to you Telco switch office via non-IP connection (ATM is 53 byte packets and reassembled to 1536 bytes in your modem) MTU won't make a difference.
3. Try http://speedtest.microsoftonline.com/ (I use it at work). Note that since you connect by serial 1-bit line that speeds are in Mega bits per second NOT Mega Bytes per second: 1 (8-bit; character) Byte = 1 start bit + 8 data bits + 1 stop bit = 10 bits.
4. "Same laptop plugged in at my office will go to any website I ask it to." What's different about your office setup?
5. Like the last question. Are the ISPs different between the 2 setups? Try trace route (tracert in command prompt) to see where along the route the packet is getting stuck. It may be at the telco office.
6. All the web sites you mention are heavily javascripted and many .js and .css etc files are called to download along with the html web page itself. The Westell (and other "modems" are also routers with a firewall, that could be set to block .jar or .cab files for instace not allowing the page to finish loading.
The modem was trying to route through it's internal IP address of 192.168.1.1 which was turned off.  Wireshark helped me figure this out.  Got it stopped from trying to route like that and the problem went away.