Koozali.org: home of the SME Server
Legacy Forums => General Discussion (Legacy) => Topic started by: Gizzmo on August 10, 2005, 06:38:27 PM
-
http://www.circuitcitycredit.com
or
http://www.fnanb.com/
It was brought to my attention that somehow this site is being block, i have 3 sites running SME boxes in front and all of them cant get there....any idea whats up?
-
They resolve to a circuit city credit card page
https://service.fnanb.com/FNANB_Consumer/Login.do?PromoCode=B
Not blocked from Calgary, AB.
:hammer:
-
Service.fnanb.com could not be found....this is so weird....
-
Try https://
That's what resolved here.
-
Still no go, even pasting those links in directly fails...its just puzzling if there is some contrib or something on all 3 of these machines causing it to happen at all the sites.....
-
Gizzmo
Have you configured your workstations web browsers to use the proxy port on the sme server (rather than directly connect to Internet) ?
-
Gizzmo
Have you configured your workstations web browsers to use the proxy port on the sme server (rather than directly connect to Internet) ?
No there is no proxies setup, but i have tried using SME proxy (didnt work) and a 3rd party proxy server (didnt work) :(
-
Gizzmo
Unless you have disabled the sme server's proxy for some good reason (not really a good idea), then your web browsers should always use the sme proxy port, either by configuring the browser to Auto detect the port, or by setting the IP of the server and port 3128.
I have seen problems similar to yours with Firfoxe where users cleverly think they can bypass the server by clicking the "Connect directly to Internet" setting, and then they complain of trouble accessing various sites, particularly those requiring secure login.
-
Ok new information since I can get back to looking at this problem.
PING fnanb.com (129.33.237.91) from *.*.*.* : 56(84) bytes of data.
From 129.33.228.22 icmp_seq=1 Packet filtered
From 129.33.228.22 icmp_seq=2 Packet filtered
From 129.33.228.22 icmp_seq=3 Packet filtered
From 129.33.228.22 icmp_seq=4 Packet filtered
From 129.33.228.22 icmp_seq=5 Packet filtered
From 129.33.228.22 icmp_seq=6 Packet filtered
--- fnanb.com ping statistics ---
6 packets transmitted, 0 received, +6 errors, 100% loss, time 5054ms
[root@bambi root]# ping yahoo.com
PING yahoo.com (216.109.112.135) from *.*.*.* : 56(84) bytes of data.
64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=1 ttl=52 time=58.8 ms
64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=2 ttl=52 time=45.2 ms
64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=3 ttl=52 time=45.9 ms
--- yahoo.com ping statistics ---
3 packets transmitted, 3 received, 0% loss, time 4387ms
rtt min/avg/max/mdev = 45.245/50.015/58.850/6.258 ms
So where is this filtering occurring and why?
-
Gizzmo,
Have you looked here, seems to be same problem, you may need to upgrade to e-smith-tinydns-0.5.0-13.noarch.rpm if you hav'nt already.
http://forums.contribs.org/index.php?topic=27117.msg119656#msg119656
Regards
Jack
-
Gizzmo, jackl
> e-smith-tinydns-0.5.0-13.noarch.rpm
Charlie says that's for sme 7.
I can access those sites quite OK with sme 6.0 and I'm using
e-smith-tinydns-0.5.0-12.noarch.rpm
You might also like to update to this:
e-smith-dnscache-0.3.0-04.noarch.rpm
See
http://forums.contribs.org/index.php?topic=27117.msg119493#msg119493
which also has the warning about the correct version of e-smith-tinydns to use.
By the way, is your sme server configured to be the DNS server, check the config in server manager/Review configuration.
-
Thanks Ray,
Sorry my mistake I referred to wrong post and update, I should have read it more carefully, in too much of a hurry these days
Thanks
Jack
-
FIXed! via this thread i stumbled onto http://forums.contribs.org/index.php?topic=27117.0
I dont know why that didnt come in any of my updates??
-
The maintenance process for 6.x is now working on making available packages to resolve Bugs raised in the Bug Tracker.
Due to limited volunteer time it has taken time to resolve the backlog of issues.
You should see packages entering the testing queue soon and the fixes for this problem are amongst the packages being considered.
-
I have tried updating TinyDNS and enable/disable/clear cache of Squid, but i still cannot reach certain web sites, and its causing major problems for my web designers inhouse who need to access admin pages for web hosting.
So I guess I have to wait and see for updates that hopefully will fix this problem on SME 6.0.
I have in the meantime connected my designers thru a netgear router to bypass the SME router, and they can login and work on the site without problems.
-
Could you state the versions of e-smith-tinydns and e-smith-dnscache that you have.
Could you also give an example web-site that you cannot reach.
I am not aware of remaining problems, for instance the two URLs given at the start of this thread
http://www.circuitcitycredit.com
or
http://www.fnanb.com/
I could not reach, but after installing
ftp://ibiblio.org/pub/linux/distributions/smeserver/releases/6.5RC1/os/e-smith/RPMS/e-smith-dnscache-0.3.0-04sme02.noarch.rpm
ftp://ibiblio.org/pub/linux/distributions/smeserver/releases/6.5RC1/os/e-smith/RPMS/e-smith-tinydns-0.5.0-07sme01.noarch.rpm
then clear the browser cache and
/etc/e-smith/events/actions/dnscache-conf
Then I could reach them OK. I can also reach http://www.nissanusa.com/
The updates are being tracked via these two reports
http://no.longer.valid/mantis/bug_view_page.php?bug_id=0000285
http://no.longer.valid/mantis/bug_view_page.php?bug_id=0000299
Once the RPMs have been through the testing queue they can be installed via yum.
I hope this helps
-
bugme
>..I have tried updating TinyDNS...
Can't you read ?
The advice is NOT to update tinydns but IS to update e-smith-dnscache !
I can access those sites quite OK with sme 6.0 and I'm using
e-smith-tinydns-0.5.0-12.noarch.rpm
You might also like to update to this:
e-smith-dnscache-0.3.0-04.noarch.rpm
See
http://forums.contribs.org/index.php?topic=27117.msg119493#msg119493
Download from
http://distro.ibiblio.org/pub/linux/distributions/e-smith/devel
rpm -Uhv e-smith-dnscache-0.3.0-04.noarch.rpm
/etc/e-smith/events/actions/dnscache-conf