Jikes!
Yes I have seen similar problems too - it never occured to me that mtu could do this - bad speed with the wrong mtu - yes but this......
I have to find the others and tell them to check this post
ping OK / firefox NOK
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
-
benJ
Re: ping OK / firefox NOK
Good Evening,
I was excited because mtu was set to 1500 so it was my last hope to find the solution.
unfortunately it still doesn't work. you'll find below the result of ifconfig on my station:
eth0 Link encap:Ethernet HWaddr 00:08:a1:2c:bb:61
inet addr:192.168.1.225 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1
RX packets:44 errors:0 dropped:0 overruns:0 frame:0
TX packets:106 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6614 (6.4 KB) TX bytes:11285 (11.0 KB)
Interrupt:20 Base address:0xa000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:200 (200.0 B) TX bytes:200 (200.0 B)
when I go to "configure" menu of eth0 in network tools. I've got a message saying my NIC is not found or doesn't work on my station...
I think i'll try to make a full re-install. don't you think?
ben
I was excited because mtu was set to 1500 so it was my last hope to find the solution.
unfortunately it still doesn't work. you'll find below the result of ifconfig on my station:
eth0 Link encap:Ethernet HWaddr 00:08:a1:2c:bb:61
inet addr:192.168.1.225 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1
RX packets:44 errors:0 dropped:0 overruns:0 frame:0
TX packets:106 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6614 (6.4 KB) TX bytes:11285 (11.0 KB)
Interrupt:20 Base address:0xa000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:200 (200.0 B) TX bytes:200 (200.0 B)
when I go to "configure" menu of eth0 in network tools. I've got a message saying my NIC is not found or doesn't work on my station...
I think i'll try to make a full re-install. don't you think?
ben
-
Husse
Re: ping OK / firefox NOK
Yeah - something seems to be really broken
First check the md5sum of the iso so it's not a bad download - it can be that....
First check the md5sum of the iso so it's not a bad download - it can be that....
-
benJ
Re: ping OK / firefox NOK
I checked md5 before...
I made other tests, and I've got the same problem with the liveCD of MINT.
I tried also a liveCD of an other distro (Fedora10) and I've no access to network.
the problem might come from the use of my NIC under linux environment?! (it's working fine with win2K)
If it's the case do you know which file I have to edit to check/modify NIC settings (drivers,...)?
Regards, ben
I made other tests, and I've got the same problem with the liveCD of MINT.
I tried also a liveCD of an other distro (Fedora10) and I've no access to network.
the problem might come from the use of my NIC under linux environment?! (it's working fine with win2K)
If it's the case do you know which file I have to edit to check/modify NIC settings (drivers,...)?
Regards, ben
-
Husse
Re: ping OK / firefox NOK
This has taken a long time - sorry
We may have to conclude it's a hardware problem
Can you run lspci and lsusb in a terminal and post here
You may have to save it somewhere to be able to post it
The simplest way to do that is to add >> somefile.txt to the commands above
somefile.txt ends probably up in home (depends on where the terminal "stands") - of course use different names
We may have to conclude it's a hardware problem
Can you run lspci and lsusb in a terminal and post here
You may have to save it somewhere to be able to post it
The simplest way to do that is to add >> somefile.txt to the commands above
somefile.txt ends probably up in home (depends on where the terminal "stands") - of course use different names