Ok Guys & Gals, first of all I'm not a coder/developer. I don't do web pages. I'm a network engineer that unfortuantly got stuck with the following issue.

Background:

*Reciving php errors VIEWING web pages, we are not hosting.
(1) Internet access via (Proxy) Novell Bordermanager ver 3.60a.
(2) Approx. 07/28/03 - end users started complaing about going to different sites and receiving "blank pages", the common factor is that they ended with (web site address)/default.php.
(3) No changes/upgrades made to our proxy.

I've been researching .php and I've kinda understand what it is and what it's for, and based on my limited knowledge and research, I think the problem is coming from the orginating web site. Maybe bad .php coding?

BTW- I can go to other sites that have .php extentions and view their materail w/o any issues.

Can anyone confirm this thought. PHP is on the server side and not the client side, having a proxy on the client side shouldn't cause any problems.

I would appreciate any thought on the subject. 😕

THX

    so this problem is only on one site, or a number of sites with .php

      Being the network engineering guru that you are, I think you answered your own question...

      I can go to other sites that have .php extentions and view their materail w/o any issues.

      Maybe post some of the problematic URLs in question, so we can all take a gander. I am behind a Cisco PIX4 Firewall, so I can shed some light from that direction...

        multi- site (at least two that I know of)

        www.home.com
        www.stbernard.info (no problem going to www.stbernard.com)

        It gets even better,

        Yesterday, it was four sites,
        www.home.com
        www.stbernard.info
        www.armedicalboard.org
        www.state.ar.us

        We downed BorderManager and cleared the proxy cache yesterday. That "seemed" to clear the issue with www.armedicalboard.org and www.state.ar.us, but not the other two.

        Today I tested other php sites; http://www.blazonry.com/index.php
        http://www.weberdev.com/ViewArticle.php3?ArticleID=369
        (at least I assume they are, based on the .php extentions in the address)

        They opened without any trouble.

        To make this look more and more like a Bordermanager / ISP related issue, when we PCAnywhere to a machine offsite and try to go the above mentioned sites (www.home.com and
        www.stbernard.info) they work. (Different ISP and no Novell Bordermanger proxy):rolleyes:

        THX for asking

          well, and if you are there now, you are using a .php site also

            hmmm...there has to be something funky with your proxy

              Yup... I can pull everything up here just fine excapt www.home.com

              The home.com one is coming up with a DNS error for me, but the rest appear to be coming up fine.

                Well after it is Novell. : ) Actually, I kinda thinking the same thing, but one thing still confuses me, why would it work on some php sites and not others? Uhmmm??? I've got a call into Novell at the moment. We'll see what they think.... Who knows, over the past 16 years I've seen Novell products do some stange things.

                Thanks for the input you guys, it always helps to get a different angle on things.

                😉

                  i'm not sure it is a php thing as your proxy thing, your browser really doesn't care if it calling php, asp, cgi, pl, etc... whatever, since all those are server side and doesn't matter to anything

                    Well, it doesn't matter about contacting Novell anyway. We are currently running Bordermanger 3.60a - which btw it reached it's "end of life" last month.

                    Another engineer and I continued to do some troubleshooting. Here's what we found out so far.

                    (1) - DNS Ping from the work station (ie; www.stbernards.info) gets resloved by our Microsoft DNS server and returns the correct IP address.
                    (2) - DNS Ping from our Proxy (Bordermanger) does not get the correct ip address, matter of fact, its an address from a web hosting company in CA.

                    I contacted the hosting company and they said it belonged to a "customer" of theirs and asked me to send a description of what was going on and they would open a ticket to investigate. It kinda sounds like the http address has been hi-jacked. :rolleyes:

                    After some more troubleshooting, we removed the secondary DNS server address (one of our own) out of the DNS list for Bordermanger and tested the http address again, this time it opened without and errors (defalut/php exetions).

                    Now the really funny thing happened, when we did a ping from Bordermanger to the ip address (stbernards) again, it still returns the bogus ip address of the server in CA. Go figure..

                    Anyway, we'll be continuing our troubleshooting in the morning. If you would like to keep up on whats going on, just post back to this message.

                    I never really though that it could be several bad .php coded pages showing up at the same time, but according to the other "folks" here, no one has made any changes to our proxy and DNS servers. Of course we run a full virus scan on boxes nighly (current dat files) and nothing is showing up strange.

                    Don't you just love technology......😃

                      Now the really funny thing happened, when we did a ping from Bordermanger to the ip address (stbernards) again, it still returns the bogus ip address of the server in CA. Go figure..

                      I am not sure how Novell Bordermanager works, but do you think it may just still be harboring cached DNS info? Is there a way to flush the DNS in there?

                        Write a Reply...