1/6/2024 0 Comments Network port mapHowever I couldn't find an option in my Verizon Actiontec MI424WR to support NAT-PMP they required for this, so for the meantime I uninstalled Access Agent 2.0.1 (26213). Parallels contacted me quickly and asked me to try manually defining an NAT rule in my router. I put in for both a problem report and a support ticket. Parallels is a good company with some really useful products - I hope they can resolve this problem soon! It appears not to handle more than one computer at a time on a LAN, which unfortunately pulls this application out of an IT pro's toolkit. At this point, it's a strictly a single user / single computer product. Something in the code appears to have changed, causing this issue. I ran two Access Agent systems on my LAN earlier in the year with no problem until sometime in July. But while I'm not using, my paid subscription ticks away. It's crazy! Given what I noted above re: my router, the only way I can eliminate it is to uninstall the Access Agents from my systems and not use the product. But instead of settling on and agreeing to use what they've already opened, they keep polling and negotiating until hundreds of ports are created. However, it seems that they must somehow be continuously polling and discovering each other, and the Agents then decide to open the next highest port to again avoid conflict. *BUT* if two systems are running Access, they seem to be fighting for that same port, and have to negotiate and agree to each map their own ports in the router. I think what I'm observing shows that if only installed on one system on the LAN, Access doesn't need to punch a hole in the router, it must somehow discreetly use that 37370 port. The port numbers increased in value (37370, 37371, 37372, 37373, 37374, etc), with one computer's IP address claiming the even numbers, the other the odd. New multiple rules started popping up for PAX TCP & UDP port mapping tied to each computer's IP address. *However*, when I added Access to the second computer, the issue returned. When I installed it on just one computer, it functioned and there were no extra rules created in my router's Port Forwarding section. I checked back this evening and found Access had been updated to 2.0.1 (26400), so I decided to give it a try. So, here's my current status with this problem. I've replicated it independently on 2 separate computers by uninstalling & reinstalling with the same results, so I'm pretty certain it's not just a one-time fluke.Ĭlick to expand.I put in for both a problem report and a support ticket. I have created a problem report & support request about this as well to document with them. Has anybody else seen this, or have any info on it? It seems like a bug. This seems to have cropped up in the 2.0.1 (26213) version of the agent. I've removed Access from my Macs to keep my port forwarding table from getting stomped all over, but now can't use my Access app/subscription, which is frustrating. The 37xxx refers to numbers that went from 37370 to 37450.Īt first I fretted, and after battening down my hatches found that they were being created by Parallels Access Agent on my 2 Macs - a new, different rule automatically about every 2-3 minutes. I was reviewing my router's firewall's port forwarding rules and saw over 250 rules residing there, not created by me.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |