Sure enough.. I quickly broke out the real code from the integrated udp scanner, and its doing great. For some reason, the way I implemented the integration is not flying. I have to think of an alternative for the tcp scanner, which then will immediately apply to the UDP. So now I know why it works for some, and not for others. That's ok, I'll have them both worked out in a couple days.

You know what.. here is the standalone udp scanner (not site integrated):

/modules/UDP_Scanner/paul.php

Try it out, let me know what you get.

Thanks Paul,
I 'll try later but don't spoil you week end on this problem
Even an expert like you needs and deserve some relaxing time
Regards

oops,
I made a mistake again the "guest" was me
Sorry,

... I have never been able to run a port scan from the site ... I'm in Pa, doesn't matter signed in or not, day or night ... I get this every time :

Your authorization was not supplied, or network is currently congested.

... but I just got a scan to run by using the standalone link Z-X posted ... seems like it's gonna take a long time ... will let you know ...

Ok.. I've reworked the UDP code for all the UDP scan options. Can you try them from lowest to highest and let me know?

... maybe tomorrow - right now, I'm caught up in some bizarre loop ... seems TWO scans are chasing themselves around my firewall ... tried to stop one, or both - no luck ... closed browser, no luck ... they're about 180 ports apart ... it's like a dot race, actually ... ...

... that was less than fun ... musta been my fault, maybe I double-dipped ...
...

Sigh... this thing will be conquered yet! Ok.. I reworked the same new code into the trojan tcp scanner, as well as a plain port range tcp scanner.. I'm seeing the same problems.

Hrumph. Well, at least I think I'm closer.

... don't run these tests late at night, when your STUPID quotient goes up sky-high ! ...

... ummm, Proxo blocks the referrer ... ...

... something's running again - either the new site test, or the dot race revisited ...

... I hear my pillow calling my name ... here, dummy ... here, dummy ...

... ...

... this morning, with Proxo bypassed, the 10 port scan hit my firewall 139 times ... from 55555 to 55564, then from 130 - 136, then 140 ... these 8 ports repeated 5 times, but 140 dropped on the last scan ... seems like more than 10 to me ...

... I did that netBEUI tweak to close port 139, I think it was ... maybe that's why there's a gap there (??) ... anyway, there ya go ... sure glad I didn't hit the 100 port scan button - we'd be here all day ...

... ...

... PS ... and hitting the stop button on my browser did not stop the test - neither did closing the browser entirely ... FYI ...

The scanner sends out the packets quickly, so by the time you stop the scan, there are many packets on the way still to your system.

Hm... I'll get it right yet.

I had similar problems running scans as referred to in this string. I traced my problems to ZAP3, after disabling cookie control and ad blocking in ZAP3 the tests appear to be running ok.

Good.. just to confirm, I don't run any ads on the site, nor are there any third party cookies.. its all first party (CCSP). I require that a CCSP referer url be passed to the scans because it enforces the "authorization" agreement.