This has got me stumped, I hope somebody can suggest something.

I have got Slackware 10 and a new adsl connection. Everything works fine except when I try to connect to any https site such as Gmail the browser comes back with a "Could not connect to server" error after a few minutes or just stays in the loading state forever. I have tried disabling the firewall but that makes no difference. I have tried with Firefox, Konquerer, Galleon and Opera.

I have verified it is not being blocked by the router because when I plug in an XP laptop I can go right to Gmail (with Firefox and IE) with no problems, also the router does not have any firewall rules configured.

Now, the wierd part is that if I go back to my old dial-up I can get right into Gmail and any other https site without problems (same ISP).

I have tried restarting the network (about a zillion times!) with rc.inet1 restart but nothing helps.


If you know what I am missing or can point me to something to read I will be vey, very grateful!

Thank you,
Mark

you may want to check your DNS servers. I think in slackware they are in /etc/resolv.conf but i am not sure. Try to go to a website by its ip address instead of its domain name. if it loads, you have the wrong dns ip addresses set up.

Are you using any proxies?

Many thanks for the suggestion, currently (using the adsl) my resolv.conf file contains
which is the router's IP address. The router had to have the DNS servers set manually. The thing is that it is working perfectly for my wife on her XP box.

I tried going to gmail by entering it's IP directly but no joy, same result.

Try changing the nameservers in the resolv.conf to those of your ISP.

Can you give us an output of ifconfig? It may be an MTU issue, since HTTPS websites have the Do not fragment flag set, they can be sending packets larger than your MTU and in turn they are not getting through. If you have name resolution for everything else on the internet, I don't see how it can be a nameservice issue.

That did it!! Thank you so much gmcmaster.

Original resolv.conf was one line, the IP of the router(192.168.1.1).

After your suggestion and reading the man page of resolv.conf I put in the two IP addresses that the ISP gave me to configure the router and Bingo! all those https sites magically started resolving.

Thank you again,

Mark

oops, weird though.

Definitely weird Sal, www.pandora.com, gmail and the control panel of my own page ie www.***etc.com:2082 all weren't working but now they are.

Anyhoo, cool beans and major thanks again to gmcmaster for the tip/help.