Remote peer is no longer responding

I have the Microsoft MN-820 Wireless Router. Whenever I
try to connect to my works VPN, I get the following
message "Remote peer is no longer responding." I am using
Cisco Systems VPN Client. I have unplugged the router and
plugged directly in the DSL modem and that works fine. So
I know it is a router issue. Any suggestions? Thanks.

Brian

Are you connecting wired or wireless on that computer?

Which version of Windows is it running? If you are running Windows XP
have you installed all of the latest updates including SP1? One way to
check if you are up to date is browse Internet Explorer to
http://windowsupdate.microsoft.com and check for updates. One of the
windows XP updates fixes several issues with a wireless connection.

If you are running wireless are you using any security? If it is a
wireless connection and you are using security what kind of security are
you using?

Does your VPN require port forwarding or does it require the router to
have some feature from a Cisco source?

After answering these questions we might have a better idea on how to
help you out with this issue.

Brian wrote:
> I have the Microsoft MN-820 Wireless Router. Whenever I
> try to connect to my works VPN, I get the following
> message "Remote peer is no longer responding." I am using
> Cisco Systems VPN Client. I have unplugged the router and
> plugged directly in the DSL modem and that works fine. So
> I know it is a router issue. Any suggestions? Thanks.
>
> Brian
>

I am connecting wireless. I am running Windows XP SP-1
with the latest updates. The router is up to date with its
software. I am not using any kind of security packages. I
am using Cisco Systems VPN client v.3.6.2. I do not know
if the VPN requires port forwarding or not. I have messed
around with that on my router and it did not seem to work.
BBut I really did not know what I was doing because I did
not know what outbound ports and inbound ports to use.
While you cannot disable the firewall, you can disable the
firewall rule that blocks ping and other ICMP commands. I
have block ICMP commands checked.
>-----Original Message-----
>Are you connecting wired or wireless on that computer?
>
>Which version of Windows is it running? If you are
running Windows XP
>have you installed all of the latest updates including
SP1? One way to
>check if you are up to date is browse Internet Explorer
to
>http://windowsupdate.microsoft.com and check for
updates. One of the
>windows XP updates fixes several issues with a wireless
connection.
>
>If you are running wireless are you using any security?
If it is a
>wireless connection and you are using security what kind
of security are
>you using?
>
>Does your VPN require port forwarding or does it require
the router to
>have some feature from a Cisco source?
>
>After answering these questions we might have a better
idea on how to
>help you out with this issue.
>
>Brian wrote:
>> I have the Microsoft MN-820 Wireless Router. Whenever I
>> try to connect to my works VPN, I get the following
>> message "Remote peer is no longer responding." I am
using
>> Cisco Systems VPN Client. I have unplugged the router
and
>> plugged directly in the DSL modem and that works fine.
So
>> I know it is a router issue. Any suggestions? Thanks.
>>
>> Brian
>>
>
>.
>

Are using WEP or WPA for your wireless security? If you are using WPA
you can enable 802.1x authentication. Otherwise you will need to be on
a wired connection with the 802.1x authentication enabled. If you need
persistent port forwarding your IT department might know. Most likely
you will only be able to connect one computer at a time to the VPN.

(E-Mail Removed) wrote:
> I am connecting wireless. I am running Windows XP SP-1
> with the latest updates. The router is up to date with its
> software. I am not using any kind of security packages. I
> am using Cisco Systems VPN client v.3.6.2. I do not know
> if the VPN requires port forwarding or not. I have messed
> around with that on my router and it did not seem to work.
> BBut I really did not know what I was doing because I did
> not know what outbound ports and inbound ports to use.
> While you cannot disable the firewall, you can disable the
> firewall rule that blocks ping and other ICMP commands. I
> have block ICMP commands checked.
>
>>-----Original Message-----
>>Are you connecting wired or wireless on that computer?
>>
>>Which version of Windows is it running? If you are
>
> running Windows XP
>
>>have you installed all of the latest updates including
>
> SP1? One way to
>
>>check if you are up to date is browse Internet Explorer
>
> to
>
>>http://windowsupdate.microsoft.com and check for
>
> updates. One of the
>
>>windows XP updates fixes several issues with a wireless
>
> connection.
>
>>If you are running wireless are you using any security?
>
> If it is a
>
>>wireless connection and you are using security what kind
>
> of security are
>
>>you using?
>>
>>Does your VPN require port forwarding or does it require
>
> the router to
>
>>have some feature from a Cisco source?
>>
>>After answering these questions we might have a better
>
> idea on how to
>
>>help you out with this issue.
>>
>>Brian wrote:
>>
>>>I have the Microsoft MN-820 Wireless Router. Whenever I
>>>try to connect to my works VPN, I get the following
>>>message "Remote peer is no longer responding." I am
>
> using
>
>>>Cisco Systems VPN Client. I have unplugged the router
>
> and
>
>>>plugged directly in the DSL modem and that works fine.
>
> So
>
>>>I know it is a router issue. Any suggestions? Thanks.
>>>
>>>Brian
>>>
>>
>>.
>>

Okay, I had to breakdown and call Microsoft. What the fix
is that under Application-triggered port forwarding you
have to put in two entries. Outbound port 500 and 10000
have to added. Inbound port also have to 500 and 10000.
And the trigger type and public type have to be UDP.
>-----Original Message-----
>Are using WEP or WPA for your wireless security? If you
are using WPA
>you can enable 802.1x authentication. Otherwise you will
need to be on
>a wired connection with the 802.1x authentication
enabled. If you need
>persistent port forwarding your IT department might
know. Most likely
>you will only be able to connect one computer at a time
to the VPN.
>
>(E-Mail Removed) wrote:
>> I am connecting wireless. I am running Windows XP SP-1
>> with the latest updates. The router is up to date with
its
>> software. I am not using any kind of security packages.
I
>> am using Cisco Systems VPN client v.3.6.2. I do not
know
>> if the VPN requires port forwarding or not. I have
messed
>> around with that on my router and it did not seem to
work.
>> BBut I really did not know what I was doing because I
did
>> not know what outbound ports and inbound ports to use.
>> While you cannot disable the firewall, you can disable
the
>> firewall rule that blocks ping and other ICMP commands.
I
>> have block ICMP commands checked.
>>
>>>-----Original Message-----
>>>Are you connecting wired or wireless on that computer?
>>>
>>>Which version of Windows is it running? If you are
>>
>> running Windows XP
>>
>>>have you installed all of the latest updates including
>>
>> SP1? One way to
>>
>>>check if you are up to date is browse Internet Explorer
>>
>> to
>>
>>>http://windowsupdate.microsoft.com and check for
>>
>> updates. One of the
>>
>>>windows XP updates fixes several issues with a wireless
>>
>> connection.
>>
>>>If you are running wireless are you using any
security?
>>
>> If it is a
>>
>>>wireless connection and you are using security what
kind
>>
>> of security are
>>
>>>you using?
>>>
>>>Does your VPN require port forwarding or does it
require
>>
>> the router to
>>
>>>have some feature from a Cisco source?
>>>
>>>After answering these questions we might have a better
>>
>> idea on how to
>>
>>>help you out with this issue.
>>>
>>>Brian wrote:
>>>
>>>>I have the Microsoft MN-820 Wireless Router. Whenever
I
>>>>try to connect to my works VPN, I get the following
>>>>message "Remote peer is no longer responding." I am
>>
>> using
>>
>>>>Cisco Systems VPN Client. I have unplugged the router
>>
>> and
>>
>>>>plugged directly in the DSL modem and that works fine.
>>
>> So
>>
>>>>I know it is a router issue. Any suggestions? Thanks.
>>>>
>>>>Brian
>>>>
>>>
>>>.
>>>
>
>.
>