Re: Re: mysql_connect does not connect

"Andrew Kreps" <andrew.kreps@gmail.com> wrote in message news:3f0cd6910409141129174d9cb9@mail.gmail.com... > On Tue, 14 Sep 2004 10:11:24 -0700, Sam Hobbs <socalsam@gmail.com> wrote: >> Also, are the warning messages documented? As I asked in my original >> question, is 10061 an error code? > > 10061 is a generic winsock error for a timeout, it's not PHP or MySQL > specific. It means that the call couldn't connect to the socket you > were trying to hit within the time allowed. Again, thank you. Apparently there is a problem with the internet being accessed. I tried to determine the problem but it is not clear. What I did to try to diagnose the problem is that I deleted from ZoneAlarm the configuration for the relevant programs. For those not familiar with ZoneAlarm, I essentially removed from it anything it knew about Apache, MySQL and php. I thne tried the mysql_connect, and ZoneAlarm asked if Apache could access the internet. However it behaved differently, depending on whether I was using an account with administrator privileges. If I was using administrator privileges, Apache tried to connect to address 0.0.0.0. If I was not using administrator privileges, Apache tried to connect to the DNS server address. However there are more details so assuming this is a bug I need to coordinate with someone to determine how to diagnose this. By removing Apache, MySQL and php from ZoneAlarm and then allowing Apache to access the internet when I did the mysql_connect, I am able to connect. I assume that this is not how it should be.