Internet Connection Sharing: "Generic Host Process... has encountered a problem and needs to close

P

Philip Herlihy

Problem: Soon after a client computer attempts to connect to the Internet
via my Internet-Connection-Sharing host, the host throws up a dialogue box
"Generic Host Process for Win32 .. has encountered a problem and needs to
close" (or something very similar). Neither client nor (usually?) host can
subsequently connect to the Internet; the connection is shown as "Connected"
in the Network Connections view, but I can't make it disconnect without
rebooting. Sometimes the client can connect for a while, before the
failure. If the broadband connection isn't running, it appears that the
client spontaneously connects to the Internet, as a "Connect?" dialogue
appears on the host. "Generic Host Process..." turns out to be svchost
running one or more dlls.

Nothing relevant can be recognised in the event log. Lengthy searches of
TechNet CDs, google.com/microsoft and support.microsoft.com have drawn a
blank. So did a detailed comparison of process listings before and after.
Any ideas?

Configuration:

Host: Windows XP Professional (SP1) patched-up-to-date, connecting to
BTOpenworld Broadband via USB ("squashed" frog modem). Ethernet connection
to client via crossover cable. TCP/IP is the only protocol installed.
Firewall: ZoneAlarm Pro (configured for ICS). Switching ICS to another
(dial-up) connection also brought up the failure dialogue. IP: 192.168.0.1

Client: Windows 95 (blush), firewall ZoneAlarm (free). Printing and
file-sharing works ok. IPX and NETBEUI also installed. File and Printer
Sharing and Windows Client installed. Obtains IP address from host.

Grateful for any ideas!
 
D

Derek

On Sun, 24 Aug 2003 12:43:49 +0000 (UTC), "Philip Herlihy"

Problem:
"Generic Host Process for Win32 .. has encountered a problem and needs to
close" (or something very similar). Neither client nor (usually?) host can
subsequently connect to the Internet;
Nothing relevant can be recognised in the event log.
Configuration:

Host: Windows XP Professional (SP1) patched-up-to-date, connecting to
BTOpenworld Broadband via USB ("squashed" frog modem). Ethernet connection
to client via crossover cable. TCP/IP is the only protocol installed.
Firewall: ZoneAlarm Pro (configured for ICS). Switching ICS to another
(dial-up) connection also brought up the failure dialogue. IP: 192.168.0.1

Client: Windows 95 (blush), firewall ZoneAlarm (free). Printing and
file-sharing works ok. IPX and NETBEUI also installed. File and Printer
Sharing and Windows Client installed. Obtains IP address from host.

This all looks to be as it should be.
Grateful for any ideas!

What motherboard does the XP machine use? (Some motherboards have
problems with the USB ports, and won't run with the speedtouch frog
modem)

Has the problem started recently?

Are you using the latest drivers for the speedtouch frog?

They should be available at <http://www.speedtouchdsl.com/>

(I say should because the site seems to be having some problems at the
moment)

Derek
 
P

Philip Herlihy

Thanks for the reply. The host is a recent Dell laptop, and I've been using
the modem for 3 months without problems. I've updated the drivers within
the last 2 months. (I'll look again, though).

I had no problems with the same model laptop running Windows 2000. Can't
persuade the Missus to upgrade... (sigh)...
 
P

Philip Herlihy

I don't think that's it. The host machine is patched with everything
Microsoft offer for my machine, I have a firewall (ZoneAlarm Pro) and I've
scanned my entire machine (and the client, as a mounted drive) with the
latest Norton antivirus files. No problems if the client isn't connected,
either. Port 135 is blocked, and intrusions regularly show up (blocked) in
the firewall log. Stumped!
 
D

Derek

OK is anyone else keeping count of how many fully updated XP machines are
reporting ICS connectivity loss of some kind? I'm up to three in the last
week on this NG.

There are two recent updates that play with the networking and remote
access side of XP.

817778 (Overview of the Advanced Networking Pack for Windows XP),
which alters both the TCP/IP stack and the XP built-in firewall.

823980 (MS03-026: Buffer Overrun in RPC May Allow Code Execution),
which patches the RPC service.

I'm starting to wonder if one of them breaks ZoneAlarm.

Derek
 
D

Derek

I don't think that's it. The host machine is patched with everything
Microsoft offer for my machine, I have a firewall (ZoneAlarm Pro) and I've
scanned my entire machine (and the client, as a mounted drive) with the
latest Norton antivirus files. No problems if the client isn't connected,
either. Port 135 is blocked, and intrusions regularly show up (blocked) in
the firewall log. Stumped!

Humour me for a while, Phillip.

1) Goto Start->run.
type, including the quotes: tasklist >"my documents\tasks.txt"
then click OK.

2) Goto Start->run
type, including the quotes: tasklist /SVC >>"my documents\tasks.txt"
then click OK.

(This will create a small file in My documents, called tasks.txt,
which lists the running programs and services on your machine.)

4) Post the contents of the file "my documents\tasks.txt" here, by
cutting and pasting the file contents to a post. (Some news servers
won't allow you to post attachments to these groups)

Derek
 
R

Real nwsy

There are two recent updates that play with the networking and remote
access side of XP.

817778 (Overview of the Advanced Networking Pack for Windows XP),
which alters both the TCP/IP stack and the XP built-in firewall.

823980 (MS03-026: Buffer Overrun in RPC May Allow Code Execution),
which patches the RPC service.

I'm starting to wonder if one of them breaks ZoneAlarm.

Now why wouldn't that surprise me in the slightest.

If you google that 6 digit number I bet you'll see a few comments on sites
like annoyances.com or whatever it is.
 
P

Philip Herlihy

Thanks to Marcus, "Real Nwsy" and (particularly) Derek for your helpful
replies.

It appears to be related to ZoneAlarm Pro (including version _40_146_029 -
just out). If I shut down ZoneAlarm (and turn on the XP Firewall) the
problem goes away. Reverse those changes and it reappears, reliably.

I'm reporting the problem to the helpful folk at Zonelabs.com.

Thanks!
 
R

Rob Morley

Thanks to Marcus, "Real Nwsy" and (particularly) Derek for your helpful
replies.

It appears to be related to ZoneAlarm Pro (including version _40_146_029 -
just out). If I shut down ZoneAlarm (and turn on the XP Firewall) the
problem goes away. Reverse those changes and it reappears, reliably.

I'm reporting the problem to the helpful folk at Zonelabs.com.
In the meantime you might like to use something a bit better than the XP
firewall - Kerio Personal Firewall is good and free.
http://www.kerio.com/kpf_home.html
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top