Observed in practice

• -11002 - When the
• -11004 - When UPnP is disabled in the router
• -11010 - When there's no UPnP (e.g. on mobile data)
• -11011
  • When UPnP is disabled in Parsec but is available on the router
  • When the user is on a guest network

Original

10XXX (range for errors from the actual router)

• -10402: UPnP: Add Port Mapping Failed: Invalid Args - See UPnP Device Architecture section on Control.
• -10501: UPnP: Add Port Mapping Failed: Action Failed - See UPnP Device Architecture section on Control.
• -10606: UPnP: Add Port Mapping Failed: Action not authorized - The action requested REQUIRES authorization and the sender was not authorized.
• -10715: UPnP: Add Port Mapping Failed: WildCardNotPermittedInSrcIP - The source IP address cannot be wild-carded
• -10716: UPnP: Add Port Mapping Failed: WildCardNotPermittedInExtPort - The external port cannot be wild-carded
• -10718: UPnP: Add Port Mapping Failed: ConflictInMappingEntry - The port mapping entry specified conflicts with a mapping assigned previously to another client
• -10724: UPnP: Add Port Mapping Failed: SamePortValuesRequired - Internal and External port values must be the same
• -10725: UPnP: Add Port Mapping Failed: OnlyPermanentLeasesSupported - The NAT implementation only supports permanent lease times on port mappings
• -10726: UPnP: Add Port Mapping Failed: RemoteHostOnlySupportsWildcard - RemoteHost must be a wildcard and cannot be a specific IP address or DNS name
• -10727: UPnP: Add Port Mapping Failed: ExternalPortOnlySupportsWildcard - ExternalPort must be a wildcard and cannot be a specific port value
• -10728: UPnP: Add Port Mapping Failed: NoPortMapsAvailable - There are not enough free ports available to complete port mapping.
• -10729: UPnP: Add Port Mapping Failed: ConflictWithOtherMechanisms - Attempted port mapping is not allowed due to conflict with other mechanisms.