Dlink.....Dlink....Dlink..... Or buy professional equipment.....:) -----Original Message----- From: isapros-bounce@xxxxxxxxxxxxx [mailto:isapros-bounce@xxxxxxxxxxxxx] On Behalf Of Amy Babinchak Sent: Friday, December 15, 2006 9:29 AM To: isapros@xxxxxxxxxxxxx Subject: [isapros] Re: Anyone Speak Linksys? NetGear is the one brand that I've never been able to get to work. We've always chosen Linksys for the micro branch offices. Which NetGear model works for you? When I tried them we got wireless or VPN client access out of them but not both at the same time. NetGear said it was a known issue and they didn't have solution at the time. Amy Babinchak Harbor Computer Services 248-546-6056 Office 248-890-1794 Mobile ISA: http://isainsbs.blogspot.com for Clients: http://smalltechnotes.blogspot.com Website: http://www.harborcomputerservices.net -----Original Message----- From: isapros-bounce@xxxxxxxxxxxxx [mailto:isapros-bounce@xxxxxxxxxxxxx] On Behalf Of John T (Lists) Sent: Friday, December 15, 2006 1:19 AM To: isapros@xxxxxxxxxxxxx Subject: [isapros] Re: Anyone Speak Linksys? I choose Netgear. Seriously. John T eServices For You "Life is a succession of lessons which must be lived to be understood." Ralph Waldo Emerson (1802-1882) > -----Original Message----- > From: isapros-bounce@xxxxxxxxxxxxx [mailto:isapros-bounce@xxxxxxxxxxxxx] On Behalf > Of Amy Babinchak > Sent: Thursday, December 14, 2006 9:07 PM > To: isapros@xxxxxxxxxxxxx > Subject: [isapros] Re: Anyone Speak Linksys? > > DLink? Seriously? > > Amy Babinchak > > Harbor Computer Services > (248) 546-6056 office > (248) 890-1794 mobile > > http://isainsbs.blogspot.com > http://www.harborcomputerservices.net > > > > > > -----Original Message----- > From: isapros-bounce@xxxxxxxxxxxxx [mailto:isapros-bounce@xxxxxxxxxxxxx] On Behalf > Of Steve Moffat > Sent: Thursday, December 14, 2006 8:14 PM > To: isapros@xxxxxxxxxxxxx > Subject: [isapros] Re: Anyone Speak Linksys? > > Lose the Linksys, get a Dlink....:P > > They work. > > S > > -----Original Message----- > From: isapros-bounce@xxxxxxxxxxxxx [mailto:isapros-bounce@xxxxxxxxxxxxx] > On Behalf Of Amy Babinchak > Sent: Thursday, December 14, 2006 8:54 PM > To: isapros@xxxxxxxxxxxxx > Subject: [isapros] Anyone Speak Linksys? > > I've got this in my VPN log on the Linksys end of a ISA 2004 to Linksys > site-to-site VPN connection. The tunnel claims to be connected but I'm > having trouble sending data through it. Here's the log on the Linksys > side. > > Dec 14 18:37:38 2006 VPN Log received Delete SA payload: deleting > ISAKMP State #127 > Dec 14 18:37:38 2006 VPN Log Received Vendor ID payload Type = > [MS NT5 ISAKMPOAKLEY 00000004] > Dec 14 18:37:38 2006 VPN Log Ignoring Vendor ID payload Type = > [FRAGMENTATION] > Dec 14 18:37:38 2006 VPN Log Received Vendor ID payload Type = > [draft-ietf-ipsec-nat-t-ike-02_n] > Dec 14 18:37:38 2006 VPN Log [Tunnel Negotiation Info] <<< > Responder Received Main Mode 1st packet > Dec 14 18:37:38 2006 VPN Log [Tunnel Negotiation Info] >>> > Responder Send Main Mode 2nd packet > Dec 14 18:37:38 2006 VPN Log Initiating Main Mode > Dec 14 18:37:38 2006 VPN Log [Tunnel Negotiation Info] >>> > Initiator Send Main Mode 1st packet > Dec 14 18:37:38 2006 VPN Log Received Vendor ID payload Type = > [MS NT5 ISAKMPOAKLEY 00000004] > Dec 14 18:37:38 2006 VPN Log Ignoring Vendor ID payload Type = > [FRAGMENTATION] > Dec 14 18:37:38 2006 VPN Log Received Vendor ID payload Type = > [draft-ietf-ipsec-nat-t-ike-02_n] > Dec 14 18:37:38 2006 VPN Log [Tunnel Negotiation Info] <<< > Initiator Received Main Mode 2nd packet > Dec 14 18:37:38 2006 VPN Log [Tunnel Negotiation Info] >>> > Initiator send Main Mode 3rd packet > Dec 14 18:37:38 2006 VPN Log Phase 1 message is part of an > unknown exchange > Dec 14 18:37:39 2006 VPN Log [Tunnel Negotiation Info] <<< > Initiator Received Main Mode 4th packet > Dec 14 18:37:39 2006 VPN Log [Tunnel Negotiation Info] >>> > Initiator Send Main Mode 5th packet > Dec 14 18:37:39 2006 VPN Log [Tunnel Negotiation Info] >>> > Initiator Receive Main Mode 6th packet > Dec 14 18:37:39 2006 VPN Log Main mode peer ID is ID_IPV4_ADDR: > '72.158.241.2' > Dec 14 18:37:39 2006 VPN Log [Tunnel Negotiation Info] Main Mode > Phase 1 SA Established > Dec 14 18:37:39 2006 VPN Log [Tunnel Negotiation Info] Initiator > Cookies = 8829 f0cf 9dc2 73e1 > Dec 14 18:37:39 2006 VPN Log [Tunnel Negotiation Info] Responder > Cookies = 5bc7 46b1 dc42 b7d4 > Dec 14 18:37:39 2006 VPN Log initiating Quick Mode PSK+TUNNEL+PFS > > Dec 14 18:37:39 2006 VPN Log [Tunnel Negotiation Info] >>> > Initiator send Quick Mode 1st packet > Dec 14 18:37:39 2006 VPN Log IKE message has the Commit Flag set > but Pluto doesn't implement this feature; ignoring flag > Dec 14 18:37:39 2006 VPN Log [Tunnel Negotiation Info] <<< > Initiator Received Quick Mode 2nd packet > Dec 14 18:37:39 2006 VPN Log [Tunnel Negotiation Info] Inbound > SPI value = 617c35a1 > Dec 14 18:37:39 2006 VPN Log [Tunnel Negotiation Info] Outbound > SPI value = 9faea60d > Dec 14 18:37:39 2006 VPN Log [Tunnel Negotiation Info] >>> > Initiator Send Quick Mode 3rd packet > Dec 14 18:37:39 2006 VPN Log [Tunnel Negotiation Info] Quick Mode > Phase 2 SA Established, IPSec Tunnel Connected > Dec 14 18:37:39 2006 VPN Log Phase 1 message is part of an > unknown exchange > Dec 14 18:37:39 2006 VPN Log IKE message has the Commit Flag set > but Pluto doesn't implement this feature; ignoring flag > Dec 14 18:37:39 2006 VPN Log message ignored because it contains > an payload type (ISAKMP_NEXT_HASH) unexpected in this message > Dec 14 18:37:41 2006 VPN Log Phase 1 message is part of an > unknown exchange > > > > > Amy Babinchak > >