Re: Problem setting up the internet connection

Madhur wrote:
François Patte wrote:
Madhur a écrit :
Hi,

I am trying to connect to internet from RedHat Enterprise
Linux 4.0 update. I have configured my ethernet card properly. Using
the netconfig i have given the same parameters as configured in
Windows. In Windows i am able to connect to internet, and I have better
speed. After this configuration if i restart my network ..
$/etc/init.d/network restart
I am able to ping google.com
But if i try to open the web page, page is getting loaded after a long
time. Some web pages are getting browser time outs and not able to open
the page.
I want to know is there any configuration i need to do either in the
browser or the system.
I am connecting directly to the internet through the router provided by
the ISP.
have you a firewall? Try, as root, "iptables -L" command and see what
is filtered.

try also: "service iptables stop" then check your browsing speed

--
François Patte
Université Paris 5 - Paris



Hi thanks for the tips to try..
but this has not yet gained me anything..
I have firewall, i have tried all the combination by disabling the
firewall, removing ACCEPT filters but the problem persists..
I would like give some more inputs..

I have a DSL router provided by the ISP.. While the checked for the
details from ethereal, the DNS query is returning success. But none of
the HTTP request are responded by the server. Time exceeded error is
given by the server while fetching the HTTP request.. The IP address
which responds this error is same as the seconday DNS address assigned
to the router.. This is a bit confusing as i am able to ping any given
IP. ICMP packets are responded apty but only my HTTP request are
failing..
I would like to know whether route or static route configuration needs
to be done?
Please help me out of this wrangle..

Thanks Madhur

If ping works 100% then your routing is fine. If ping works 50% you have two default routes :-) Yes, it was possible on NT but I think not on Linux..

The remaining issues are firewalling and DNS normally.

If you can ping by name instead of by number, that generally means DNS is working, though you may get issues to do with caching and stale tables.

Slow loading rather than no loading is seldom an issue that has anything to do with the IP layers as such, and unless its due to having e.g. a duff nameserver entry in resolv.conf, its not due to DNS either.

Its either simply a poor browser, or its due to packet loss. Check that with "ifconfig -a" and look for high error counts.

If you have two nameservers on /etc/resolv.conf one of which isn't a valid nameserver, then you will get DNS delays as the first one times out. I strongly recommend setting up as your own DNS proxy by installing BIND anyway. This releases you from the vagaries of your ISP's servers.

As far as firewalling goes, this usually either mneans things work fine, or not at all. I cannot think of a scenario in which it slows things down, unless you have a seriously overworked firewall CPU.




..


.

Relevant Pages

  • Re: dns error
    ... If I take my firewall off ... It is very common for firewalls to block ICMP (ping and tracert); ... this is NOT a DNS issue -- DNS is working fine. ...
    (microsoft.public.win2000.dns)
  • Re: Users Internet access
    ... Users can ping the server. ... How do I check for a firewall on the DNS. ...
    (microsoft.public.windows.server.sbs)
  • Re: network goes down everyday at same time
    ... we have two firewalls (client side and server side) ... DNS all outgoing requests we use our ISPs DNS and all incomming requests we ... Windows IP Configuration ... So, next, I'd be looking at your firewall - logs, etc. ...
    (microsoft.public.windows.server.networking)
  • Re: network goes down everyday at same time
    ... we have two firewalls (client side and server side) ... DNS all outgoing requests we use our ISPs DNS and all incomming requests we ... Windows IP Configuration ... So, next, I'd be looking at your firewall - logs, etc. ...
    (microsoft.public.windows.server.networking)
  • Re: Internet Access problem on Fedora Core 4.
    ... was done to see if my DNS was misconfigured. ... I tried putting the proxy address as a value to nameserver, ... I then checked if my browser proxy configuration was set to direct ... PING 64.233.179.99 56bytes of data. ...
    (comp.os.linux.networking)