[fw-wiz] Pix - portmap translation creation failed

From: Crissup, John (MBNP is) (John.Crissup_at_us.millwardbrown.com)
Date: 02/02/04

  • Next message: Javier Sanchez Llera: "Re: [fw-wiz] Pix - portmap translation creation failed"
    To: "'firewall-wizards@honor.icsalabs.com'" <firewall-wizards@honor.icsalabs.com>
    Date: Mon, 2 Feb 2004 09:38:00 -0600
    
    

    OK, folks, need your help. We have a user trying to VPN out of our network
    using a Netscreen or SafeNet (??) client (Sorry, got that second hand and am
    not up on Netscreen products). I'm seeing a syslog entry being generated by
    the PIX for message %PIX-3-305006. The exact error follows (appropriately
    scrubbed)...

    %PIX-3-305006: portmap translation creation failed for protocol 50 src
    inside:172.20.1.1 dst outside:A.B.C.D

    My PIX 520 (Ver 6.3.1) is configured to use PAT for all Internet bound
    traffic. A search of Cisco's site turns up nothing about this particular
    error except a bug report that the documentation needs to be updated to show
    this error. Can anyone offer some direction on how to resolve this?

    As always, thanks in advance for any assistance you can offer.

    --
    John M. Crissup
    Network Systems Engineer
    Global Network Services
    Millward Brown
    535 E. Diehl Rd.
    Naperville, IL 60563
    ==================================================== 
    This email is confidential and intended solely for the use of the 
    individual or organisation to whom it is addressed. Any opinions or 
    advice presented are solely those of the author and do not necessarily 
    represent those of the Millward Brown Group of Companies.  If you are 
    not the intended recipient of this email, you should not copy, modify, 
    distribute or take any action in reliance on it. If you have received 
    this email in error please notify the sender and delete this email 
    from your system. Although this email has been checked for viruses 
     and other defects, no responsibility can be accepted for any loss or 
    damage arising from its receipt or use. 
    ==================================================== 
    _______________________________________________
    firewall-wizards mailing list
    firewall-wizards@honor.icsalabs.com
    http://honor.icsalabs.com/mailman/listinfo/firewall-wizards
    

  • Next message: Javier Sanchez Llera: "Re: [fw-wiz] Pix - portmap translation creation failed"

    Relevant Pages

    • RE: Lost my outlook contact... :(
      ... the network configuration is started from a web page located ... client computer, you will see a welcome page to invite you to start the ... local user profiles to the domain user profile. ... Before joining client computers to the network, ...
      (microsoft.public.windows.server.sbs)
    • Re: SMS 2.0 and SMS 2003 Running at same time in same domain.
      ... the clients are on the network. ... The operating system reported error 53: ... Possible cause: The client is offline. ... Verify that the client is connected to the network and that the SMS ...
      (microsoft.public.sms.setup)
    • RE: Printing from Win9x clients stops
      ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
      (microsoft.public.windows.server.sbs)
    • RE: Wireless Security Notes and Findings (from this list and other places)
      ... There are two general areas of wireless security: Authentication and ... authentication standard that works with wireless networks. ... client computer runs a client program to connect to the network with a ...
      (Security-Basics)
    • Re: Small business thinking about backing up data, having a server and 2-3 users - is SBS200
      ... is networked to the Master with a crossover network cable. ... Master on the Master PC and Client on the Slave pc. ... Since this machine is a server is should handle the requests ok ... Most real firewall appliances have HTTP and SMTP proxy services that allow ...
      (microsoft.public.windows.server.sbs)