• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Some UDP ports reported open by Sygate Scan

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

Hellboy

Registered
Joined
Feb 8, 2005
Location
Malta
Hi, need a little help!
Originally my computer was connected directly to the internet via an adsl modem, and scanning my UDP ports using http://scan.sygate.com/ would result in all ports being blocked. This was using ZoneAlarm.

Now I have networked my old computer to this one (for d wife) and have added a router. So the setup now is both comps behind the router, which is connected to the adsl modem. But performing the same scan (UPD ports) shows most of them as closed, and 4 or 5 as open. I'm still running ZoneAlarm. Does anyone know why?

Thanks
 
??

UDP doesn't send anything back to the server under normal operation so there would be no indication if the port was "open" or not...
 
Thanks for your quick reply.
So you're saying they can't test it in the first place?
I thought UDP ports are used for on-line games, which means that for example a player's position would be sent to my computer, but wouldn't my position and action be transmitted back to the server or is it done differently ...... dunno
 
The open ports are, 53, 135, 137,138,139, and 445. The rest are all closed but they used to be blocked!
 
135,137,138,139 and 445 all deals with windows file sharing and other ports. These should not be open to the internet.

So either zonealarm is for some reason not blocking these properly (even though your router is so long as you didn't forward them or put yourself in the dmz), or some how your isp is filtering them but is causing some sort of false positive (the port is blocked but the filtering method is triggering a positive responce from the scan).

I would look at your router and zonealarm first to see if something has bene changed or mis-configured.
 
Well I just went through my Router menus, and here are the results:

Port forwarding: not enabled
Virtual Server: not enabled
Special Applications: none enabled
UPnp settings: not enabled
ALG settings: none enabled
Mac filtering: not enabled
IP filtering: not enabled
URL blocking: none defined
DoS: set to block
Ping of Death: set to block
Ping from WAN: discard
Port Scan: Block
Sync flood: block
DMZ: not enabled

What kind of setting should I look for in ZoneAlarm?
None of the programs have internet server rights and most have to ask permission to access the internet. Progs that have permission to access the internet are:
Firefox
Internet Explorer
Windows Explorer
Generic Host Pro For win32
Services & Controller
Spooler Subsystem App

Don't know if all this is any help?
 
Try removing windows explorer and see if that fixes the problem.

The thing is so long as your router is ahead of your two computer (modem is plugged into the router's WAN port correct?) any attempts to connect to your computer should fail.
 
Removed windows explorer, updated router firmware, rebooted but its still the same :(
And yep modem is connected to the router WAN port, so its ADSL modem to router and then to computers.
 
I tried Shields Up site but I didn't notice any UDP port scan. All other tcp ports were blocked..ok.
Do you know any other site that scans UDP ports?
BTW thanks for trying to help out, much appriciated :)
 
Scanned comp and got the same results as sygate much quicker though. Ports open 53, 137,138,139.
135 and 445 weren't mentioned.
 
I even tried setting the router to deny UDP ports 137, 138, 139 but they are still open. I'm going to start tearing my hair out soon :((
 
If you can find another scanner that agrees with dslreports I would assume that sygate is for some reason reporting a false positive.
 
Scanned with speed guide port scan, and got the same results. Meanwhile I've been search the net and tried the following:
To close port 53, go to network icon, tcp/ip, properties,advanced,dns tab,untick <register this connections address in dns> then disable dns client from services.
I did all that but port 53 was still open
I also installed a port blocker program to block ports 137,138,139 etc
BUT it said it could not block them. Also I got a popup from zonealarm saying that this new prog wants to act as a server (but i denied, didn't understand why it needed to be a server)
 
Same ports open 53, 135, 137,138,139,445 :bang head
The port blocker is called pblocki.exe
I just ran sygate scan for trojans - none found, and performed virus scan and update, all ok
 
Last edited:
Installed Suse Linux 9.1. I scanned my ports and they were all blocked.:D I then updated linux online and when it finished I re-scanned and found all the same ports open again :temper: (53,135,137,138,139,445 all open). The interesting thing is that before performing the update this distro cannot access windows files (the connection dies suddenly) but now that it does they're all open :cry:
 
Last edited:
Back