TubeNet

rickrush wrote:TubeNet doesn't work at the Library computer. All of the others do. ???

Okay, I'm confused (gee, there's a shock, eh? ). "All of the others do" -- all of the other TubeNets?

rickrush wrote:TubeNet doesn't work at the Library computer. All of the others do. ???

Talk to the sysadmin at the library. Maybe it is being filtered for some reason.

Kevin Hendrick wrote:

rickrush wrote:TubeNet doesn't work at the Library computer. All of the others do. ???

Okay, I'm confused (gee, there's a shock, eh? ). "All of the others do" -- all of the other TubeNets?

Not to mention the ambiguity of work. I mean, what does TubeNet do when it works? If it's "make me laugh" or "make me play the tuba better", maybe these things naturally don't happen in the Library because you're trying to be quiet? If it's "make me go to sleep", then there's something wrong with the computer.

***DISCLAIMER***
The advice given is purely an exchange of knowledge. The poster does NOT accept any responsibility for any repercussions as a result of the advice provided.
***\DISCLAIMER***

Possibility #1: There is a strong possibility that your library is using some form of internet content filtering. I had converted an old desktop PC into a Slackware Linux/TinyProxy/Dan's Guardian content filter for the school I was working for. Content filters are often fed a predetermined list of known "offenders," but can be configured to block specific sites or specific content. Filtering is often done so that little Johnny can't surf his favorite fetish site while in a public place. With all of this said....why the crap would they filter out TubeNet? If they truly ARE filtering TubeNet then you will likely get a splash screen saying something like "this site has been blocked by network administrators".......unless they are using a "hosts" file (see 127.0.0.1 reference below) If it really is filtered, you can get around it by using a public proxy. (Google it at your own risk) Of course.....they maybe blocking those proxies.

Possibility #2: Bad DNS resolution. From the command prompt type "ping forums.chisham.com" You should get something like this...

todd@ubuntuman:~$ ping forums.chisham.com
PING server2.chisham.com (72.51.33.8) 56(84) bytes of data.
From 172.16.1.254: icmp_seq=1 Redirect Network(New nexthop: 172.16.1.252)
64 bytes from server2.chisham.com (72.51.33.: icmp_seq=1 ttl=56 time=69.7 ms
64 bytes from server2.chisham.com (72.51.33.: icmp_seq=2 ttl=56 time=68.8 ms
64 bytes from server2.chisham.com (72.51.33.: icmp_seq=3 ttl=56 time=68.3 ms
64 bytes from server2.chisham.com (72.51.33.: icmp_seq=4 ttl=56 time=68.4 ms
...

If the part in red is something different (possible problem) or 127.0.0.1 specifically (blocked by administrator) then the site may not be displayed. (Yeah yeah....they could have multiple IP's.)

Possibility #3: TubeNet uses modern services like javascript and CSS. The browser that you are using could 1) not support those functions or 2) have them disabled. This would make TubeNet look funky.

Possibility #4: (worth throwing this out there) You have no internet connectivity. The library computers may be set for only their intranet and Google.

Possibility #5: (As "sloan" would say) Mumble...
=========
So....what do you mean by "doesn't work?"

Your library might be blocking our porno ads.