Network access blocked.

Okay, this is what I believe to be a Windows issue rather than a Mozilla issue, but I am posting it here because it affects Mozilla, seemingly exclusivly. This is not the first time this has happened, but it's the first time I took time to do some troubleshooting on it. I leave my computer for a good while. Today, it was about 4-5 hours. When I comeback I click to open Netscape 7.1 and it immediately with no grinding at all says that pop.east.cox.net can not be found and then the browser proceeds to say the same thing about my home page ( www.shamikaserver.com ). Closed, opened, palyed, nothing. Now I know the hole to the Internet is still there because Trillian is connected and completely happy. So I try to goto Google. Google.com does not exist. I close and open Thunderbird and Firefox, same thing. I open Internet Exploiter put in Google and BAM it opens. IE will go anywhere I point it. Close and open NS again and it's still blocked. I have never used the fire wall in XP and Zone Alarm is completely turned off. I opend the network connection properties and send an IM to myself on Yahoo through Trillian and I see the packets fly past and the IM goes straight through. From this point all I can do is reboot and when it starts back up, everything is normal again. Anyone have any ideas with this??? Any and all Microsoft conspiracy theories are completely welcome

 

From your discription, I would be pretty confident in saying that it is a Mozilla problem. If you can get responses from Google searches in IE then your network connection is working - especially if you searched for something unusual the results of which wouldn't be cached somewhere.

If you can identify the Mozilla processes in Windows Task Manager, I would recommend:

Wait until the next time it happens. Close Mozilla (all Mozilla apps). Then go through the processes list and see if any of the Mozilla processes are still running. If you spot one, use the End process option. Then try opening Mozilla again and see if it works properly. If it does you've identified the offending process.

Perhaps another poster may be able to list the Mozilla processes, or you may find the information on Mozilla.org

 

Well both times it happened EVERYthing was closed. The only app running at the time was Trillian and there were no listings in the applications or processes list for it. I didn't try looking at the router from IE but I assume it would see it since it saw out to Google etc. So it's as if after sitting a while Mozilla can not get out, either by a problem of it's own or one created by Windows.

 

Forgive me if I'm teaching you something you already know, but processes used by Mozilla may not be simply labelled as being "Mozilla.exe" or similar. I was hoping someone else more familiar with the inner working might have suggested some processes. So you'll have to work it out the hard way.

Boot the system.
Open task manager and write a list of all the processes running
Then open your Mozilla apps and note all the new processes that fire up.
Then close your Mozilla apps and see if they all close. Keep a list of the "Mozilla" process and see if any of them are running when the problem arises.

If they all close, and none of them are there when the problem arises, please feel free to flame me!!!

 

Hi WindsorFox,

I think Reggie is on the same trail as I am, and that is, that Mozilla is still in the Task Manager when you try and start it again. Mozilla is listed in the Task Manager as "Mozilla ".

It seems odd that only Mozilla is kicked off, and no other programs? You said that you disabled your firewall and it wasn't blocking Mozilla. I also wonder about your Anti Virus program, and whether it could be the culprit. Do you by chance use Norton's Firewall? Also do you use Quick Launch? Disable both, then enable one at a time and see what happens, the next time this occurs.

What other third party programs do you use with Mozilla, i.e., spam blockers, web accelerators, ad/banner blockers, etc.

Don't flame Reggie, he's one of the good guys...

Ramona

 

Okay, I hadn't thought of that. From a cold boot I have 21 processes running, next time it does this I will check what is running and again after reboot and see. Don't wait up, it may be a month or more until it does this again.