Help with PProxy on Win2K pro

[Dougal]

Hi all,

I'm running a PPRoxy on my desktop machine at work running Win2K Pro. It's running as a application rather than a service as I prefer to see what's going on. Also I have to flush via a dialuip so it's comforting to see it all working properly. I have a strange problem where the PProxy appears to just stop listening to connections. I have a number of clients and another PPRoxy that flush to my machine. This morning the clients are all backed up but don't show any sign of a real error message. I forced the other pproxy to fluxh and it made a connection then just said "connection disconnected". My desktop pproxy shows no sign of a connection attempt. I tried restarting the pproxy using CTRL + BREAK but this made no difference. I shut the proxy down and restarted it and it works like a charm. 12K instantly started flooding in.

Has anyone seen this before or can anyone suggest a possible reason.

 

[imported_CyberWire]

my win2kpro box runs my entire network using ICS
it also serves as a pproxy for the round robin
and a private setiQ for my seti machines
I notice randomly when everything just stops being able to connect to the machine.
The oddest part is that ICS still works, but all other programs seem to jus stall. I can't even VNC into the box to restart it normally(no monitor on the box). I'm thinking of running 2kadvserver and seeing if that fixes the problem.

 

[MWalkden]

I would make sure you have all the fixes/patches installed. If you haven't used Microsofts new HFNETCHK tool, get it here HFNETCHK Tooland see if you are missing anything. Your problems may be application specific but sound like typical Internet hacking attempts which cause these exact symptoms on any PC behind a NAT. I've seen it on every customer's network I service and that is the only thing they all have in common is the NAT. After applying the updates I haven't had a lick of problems.

.MW

 

[imported_CyberWire]

I update as soon as patches come out
still have the same problem

 

[ViRGE]

If I remember right, the Core had the same problem once upon a time when working alongside the Dcypher pproxy. It may be that the pproxy doesn't play nicely with other programs, or other programs don't like the pproxy.

 

[Possessed Freak]

I noticed that the pproxy locked up once in a blue moon on it's own for no reason at all...

the dcphyer pproxy had some issues, and needed to be restarted every couple of days or so to keep mem usage and cpu usage down. Other than that, it behaved very nicely with dnet's pproxy. I used to run two pproxies, and 1 dcypher proxy at once, and as long as I restarted the dcypher proxy for preventive maintnance, it would run fine.