Ok, I have tried to talk to the folks at Atea, but they tells me that
this is a Linux problem. |
( Atea is the leading Nordic and Baltic supplier of IT infrastructure with approximately 5,400 employees)
When we moved in to the new school one year ago we had the same problems, the solution was to route our school on the outside of the "gateway-security-filter".
But after an "upgrade" we are forced back, and have to use the same gateway as all the other schools in the region.
Diskless Clients can surf on the Internet, but it is slow.
The server can surf on the Internet.
Laptops using Ubuntu linux on 10.0.2-network can't surf on the internet.
Ubuntu PC's can ping adresses on the outside of the filtering-gateway, and skolelinux.org resolves to 126.96.36.199
It is almost not possible to update Ubuntu PCs
It is not possible to update SLX servers, apt hangs on "waiting for headers...."
At school we have 3 different networks. One for the pupils, one for administration and theachers, and one for art/music-school.
On the two first networks I run slx-servers. The third network is administrated by the admin-staff at the town hall. When i try an Ubuntu PC at this network the same thing happens. I can ping and trace skolelinux.org, and it resolves to 188.8.131.52. But I can't surf the web, and I can't install or update software because of timeout.
All PC's and clients can with no problems view webpages that are on servers on the inside of the filtering-gateway. E.g Sunndal.kommune.no - www.tingvoll.kommune.no, www.kristiansund.kommune.no and so on...
I've tried to use rsync to get the latest DVD, but it is not possible. SSH is also blocked, so I can't use SSH to user.skolinux.no, and I can't update the schools webpage using scp....
This is so fun...
Den 17.02.11 14.30, skrev Klaus Ade Johnstad:
Torsdag 17. februar 2011 13.01.17 skrev Ole-Anders Andreassen :Things worked fine until a few days ago, then they changed someting on the outside of our network, and I have been told that everything should be transparent. OleARight, honestly, I think you should have a talk with those that changed something on the outside of your network, as the cahnage and your problem seems to coincide.