uPnP question

Soldato
Joined
1 Jun 2005
Posts
5,152
Location
Kent
When i close my torrent program i always check my netgear routers uPnP page to check to make sure the port is no longer mapped (sometimes it stays mapped and causes problems), and today i noticed for some reason on the uPnP screen it was listing port 52356 mapped to my LAN IP (and thats not my uTorrent port). I couldnt see any unusual programs running, and netstat didnt show any connections on that port, so should i be worried that it was being shown as having that port mapped to my LAN IP?

I have disabled uPnP and am using port forwarding (which doesnt seem to be working) untill i can figure out what program caused uPnP to open that port, but a google search has not realy helped me find out what program uses that port and so far my avast scan is clean.

Edit: I just got my router to email me a full log (log in the web browser screen is very limited in what it shows), and it seems that many different IPs are trying to connect on that port, as if it was a torrent program using that port, only problem is uTorrent is my only client, and that uses a single port, its not set to randomize port each startup. So i still have no clue as to the cause.
 
Last edited:
Doesn't anyone know how i can find out what is trying to use uPnP or port 52356? I've had to turn on uPnP again so that i can use torrents, but this port keeps being opened and i have no idea what it is.
 
Thankyou. I just tried that and it lists one of the svchost.exe processes using port 52356, i checked windows task managers service page and there are quite a few things all on the same process ID so im not sure which specific service is causing it, because surely it isnt right for it to be opening ports is it?

Should i be worried if i cant find out whats opening the port? both AVG and avast havnt picked up anything on their full scans, so am i worrying for nothing?
 
Last edited:
try downloading unplug and pray, i had svchost.exe using a lot of cpu and this sorted the issue out, no problems since and no access problems to the net afterwards.

always be wary if you can't find whats opening ports, no reason if its something thats needed that you shouldnt be able to identify it.
 
Last edited:
Back
Top Bottom