Re: Avaya VPN Remote Client Died After Installing SP2 On XP Pro

From: Hans-Georg Michna (hans-georgNoEmailPlease_at_michna.com)
Date: 09/08/04


Date: Wed, 08 Sep 2004 20:23:33 +0200

On Tue, 7 Sep 2004 14:43:03 -0500, "markneff"
<markneff(remove)@verizon.net> wrote:

>My Avaya VPN Remote Client software quit working after I installed SP2 on my
>XP Pro OS. I have tried it with the new firewall turned off, and with the
>new firewall turned on with exceptions, neither of which work. The Avaya
>log shows error message: "PANIC failed to initialize". The logging built
>into the firewall in the advanced settings always shows dropped packets on a
>variety of ports. I have been adding the ports in both ICMP and TCP flavors
>to the exception list using the built-in log as a guide after every attempt
>to connect. So far, I think I have added about 50 to 60 ports. I have also
>used Port Reporter and a third party port monitor program to try to zero in
>on what ports should be unblocked, but to no avail. I have also added the
>Avaya client and service programs to the firewall exceptions list. Noting I
>have tried has worked. One common behavior throughout has been that it
>appears to connect and get through the authentication process, but always
>times out while it is trying to create secure tunnels. I have a number of
>co-workers who are experiencing the same thing. Any help would be greatly
>appreciated.

Mark,

one obvious way to go is to ask the manufacturer of that VPN
client. They should know by now.

Hans-Georg

-- 
No mail, please.


Relevant Pages

  • RE: Microsoft Windows SBS 2003 Communication Issues
    ... I can't get past step three, their is NO Exceptions tab? ... Click "Windows Firewall". ... Identifying and opening ports ... > This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Firewall Problems With SBS2003 Std Server SP1
    ... While trying to Resolve an issue with Symantec Corporate configuration, ... created the exceptions and now find that the LAN clients can no ... The Ports needed for Symantec A/V Corporate Edition Are: ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows Firewall Config for Symantec AV Corp version 9
    ... Actually you need to create 2 UDP port exceptions for Corporate Edition. ... Those 2 ports are 2967 and 38293. ... If you always go to the client and run the installer from the ... I have documents from MS and Symantec that talk ...
    (microsoft.public.windows.server.sbs)
  • Re: XPsp2 - firewall enable/disable based on net
    ... That's why you configure exceptions for the local IP address range. ... requests from other addresses will be denied. ... > Ports must be available for sms and other software while on corporate ...
    (microsoft.public.windowsxp.security_admin)