1. Try
   links -dump http://www.kernel.org/kdist/finger_banner
   or
   curl http://www.kernel.org/kdist/finger_banner
   
2. Then try
   links -dump http://204.152.191.5/kdist/finger_banner
   or
   curl http://204.152.191.5/kdist/finger_banner
   
3. Also can you ping your DNS servers?

<edit> Also did you check with your college's IT on whether you need to use a proxy to access the internet?

where to try that:
and for the 3rd qstn i'll enquire and reply....

I'm having the same problem, so I'm following your moves. I was able to enter the command into the terminal as user and root:

$ lynx -dump http://www.kernel.org/kdist/finger_banner

Looking up www.kernel.org
Making HTTP connection to www.kernel.org
Alert!: Unable to connect to remote host.

lynx: Can't access startfile http://www.kernel.org/kdist.finger_banner

These are the outputs:

[root@Gejoe ~]# links -dump http://www.kernel.org/kdist/finger_banner
ERROR at dump.c:188: Host not found
[root@Gejoe ~]# links -dump http://www.kernel.org/kdist/finger_banner >ask.txt
ERROR at dump.c:188: Host not found
[root@Gejoe ~]# curl http://www.kernel.org/kdist/finger_banner
curl: (6) Couldn't resolve host 'www.kernel.org'
[root@Gejoe ~]# links -dump http://204.152.191.5/kdist/finger_banner
ERROR at dump.c:188: Permission denied
[root@Gejoe ~]# curl http://204.152.191.5/kdist/finger_banner
curl: (7) Failed to connect to 204.152.191.5: Permission denied
[root@Gejoe ~]# lynx -dump http://www.kernel.org/kdist/finger_banner
bash: lynx: command not found
[root@Gejoe ~]# $ lynx -dump http://www.kernel.org/kdist/finger_banner
bash: $: command not found



pinging primary and secondary DNS respectively:

[root@Gejoe ~]# ping 210.212.244.3
connect: Network is unreachable
[root@Gejoe ~]# ping 61.1.192.65
connect: Network is unreachable

i compiled a 2.6.13.4 kernel and the new kernel then detected the card but i was not able to ping or browse or telnet...
Then one of my lecturer from Information Technology Dept came to my room and gave these commands :
ip link help
ip link set eth0 down
ip link set eth0 up
service network restart
Then we were able to ping but not able to run telnet command.
Then he checked:
/etc/resolv.conf
and restarted the network as done earlier:
service network restart..
finally we were able to browse!!!!!!!!!!!!!!
But we found another thing that whenever i need to boot into fedora3 i
need to restart my network......only then i'll be able to browse....