VPN - host not responding MN-700

I was able to log into my VPN prior to installng the MN-
700, since then it says host is not responding when i try
to log in. I am running Windows ME. the VPN is Nortel
Contivity. I am using cable internet.
I did some reading and did one of Barb's suggestions, i
changed the IP address in LAN to 192.168.1.1 was that
right?? nevertheless it never helped, still got the same
message.
I'm new to the wireless router kinda thing, so go easy on
me...lol. Any suggestions would be great, thanks in
advance.


Mark

I'm having the same problem but with cisco vpn ... the
whole thing about the localnet addressing (192.168.*,
etc) has to do with addressing conflicts between your
local network and the network you are connecting to ...
that is they can't have similar subnets ... if the
destination network actually uses 192.168.1.* internally,
you'll want to set your router to use 192.168.2.* for
your home network ... I believe the problem lies
elsewhere though ... I think it has to do with IPSec
passthrough ... most sites suggest that you turn off XP's
ICF (Internet Connection Firewall) or any other similar
software (ZoneAlarm, etc). I tried that but it didn't do
anything for me ... I bet the router is the problem ... I
don't see a setting for IPSec passthrough anywhere ... my
LinkSys router on the other hand had that option ... the
more I use my new router the more disappointed I get
about microsoft's entry into this field ... just another
example: the router management software is very "fisher
price" ... and the broadband network utility won't see
the damn router anymore ... pretty lame. I'll let you
know if I find anything more useful than just moral
support. :P

>-----Original Message-----
>I was able to log into my VPN prior to installng the MN-
>700, since then it says host is not responding when i
try
>to log in. I am running Windows ME. the VPN is Nortel
>Contivity. I am using cable internet.
>I did some reading and did one of Barb's suggestions, i
>changed the IP address in LAN to 192.168.1.1 was that
>right?? nevertheless it never helped, still got the same
>message.
>I'm new to the wireless router kinda thing, so go easy
on
>me...lol. Any suggestions would be great, thanks in
>advance.
>.
>

I had a similar problem connecting to a client's network that was using the
192.168.2.X addressing scheme and the Quest VPN software . I resolved my
problem by creating a "Virtual DMZ" that pointed back to the IP Address of
my laptop. Once I set up the DMZ, I connected almost instantly. I kill the
Virtual DMZ after each session.

"demetrios christopher" <(E-Mail Removed)> wrote in message
news:149b701c3f8ff$88a85cf0$(E-Mail Removed)...
> I'm having the same problem but with cisco vpn ... the
> whole thing about the localnet addressing (192.168.*,
> etc) has to do with addressing conflicts between your
> local network and the network you are connecting to ...
> that is they can't have similar subnets ... if the
> destination network actually uses 192.168.1.* internally,
> you'll want to set your router to use 192.168.2.* for
> your home network ... I believe the problem lies
> elsewhere though ... I think it has to do with IPSec
> passthrough ... most sites suggest that you turn off XP's
> ICF (Internet Connection Firewall) or any other similar
> software (ZoneAlarm, etc). I tried that but it didn't do
> anything for me ... I bet the router is the problem ... I
> don't see a setting for IPSec passthrough anywhere ... my
> LinkSys router on the other hand had that option ... the
> more I use my new router the more disappointed I get
> about microsoft's entry into this field ... just another
> example: the router management software is very "fisher
> price" ... and the broadband network utility won't see
> the damn router anymore ... pretty lame. I'll let you
> know if I find anything more useful than just moral
> support. :P
>
> >-----Original Message-----
> >I was able to log into my VPN prior to installng the MN-
> >700, since then it says host is not responding when i
> try
> >to log in. I am running Windows ME. the VPN is Nortel
> >Contivity. I am using cable internet.
> >I did some reading and did one of Barb's suggestions, i
> >changed the IP address in LAN to 192.168.1.1 was that
> >right?? nevertheless it never helped, still got the same
> >message.
> >I'm new to the wireless router kinda thing, so go easy
> on
> >me...lol. Any suggestions would be great, thanks in
> >advance.
> >.
> >

The Virtual DMZ works for my laptop only i have XP pro
there, but on my desktop i tried the DMZ but it booted me
out and caused an error, i had to reboot and go through
scandisk. For the time being I will use DMZ to access my
VPN. But i was curious, if DMZ makes my network
susceptable to hackers, how much more of a risk is it for
my companies network?? my IT dept. may give me crap if it
opens a door for hackers. Or is the companies normal
protection still there.
Hey Demetrios did you try the port forwarding idea that
people were talking about??? I would try it but i don't
understand it enough to be messing with it.
>-----Original Message-----
>I had a similar problem connecting to a client's network
that was using the
>192.168.2.X addressing scheme and the Quest VPN
software . I resolved my
>problem by creating a "Virtual DMZ" that pointed back to
the IP Address of
>my laptop. Once I set up the DMZ, I connected almost
instantly. I kill the
>Virtual DMZ after each session.
>
>"demetrios christopher" <(E-Mail Removed)> wrote
in message
>news:149b701c3f8ff$88a85cf0$(E-Mail Removed)...
>> I'm having the same problem but with cisco vpn ... the
>> whole thing about the localnet addressing (192.168.*,
>> etc) has to do with addressing conflicts between your
>> local network and the network you are connecting to ...
>> that is they can't have similar subnets ... if the
>> destination network actually uses 192.168.1.*
internally,
>> you'll want to set your router to use 192.168.2.* for
>> your home network ... I believe the problem lies
>> elsewhere though ... I think it has to do with IPSec
>> passthrough ... most sites suggest that you turn off
XP's
>> ICF (Internet Connection Firewall) or any other similar
>> software (ZoneAlarm, etc). I tried that but it didn't
do
>> anything for me ... I bet the router is the
problem ... I
>> don't see a setting for IPSec passthrough anywhere ...
my
>> LinkSys router on the other hand had that option ...
the
>> more I use my new router the more disappointed I get
>> about microsoft's entry into this field ... just
another
>> example: the router management software is very "fisher
>> price" ... and the broadband network utility won't see
>> the damn router anymore ... pretty lame. I'll let you
>> know if I find anything more useful than just moral
>> support. :P
>>
>> >-----Original Message-----
>> >I was able to log into my VPN prior to installng the
MN-
>> >700, since then it says host is not responding when i
>> try
>> >to log in. I am running Windows ME. the VPN is Nortel
>> >Contivity. I am using cable internet.
>> >I did some reading and did one of Barb's suggestions,
i
>> >changed the IP address in LAN to 192.168.1.1 was that
>> >right?? nevertheless it never helped, still got the
same
>> >message.
>> >I'm new to the wireless router kinda thing, so go easy
>> on
>> >me...lol. Any suggestions would be great, thanks in
>> >advance.
>> >.
>> >
>
>
>.
>

I had a similar problem with the Netscreen client. The
problem turned out to be the network utility that
installed to setup the MN-700. I quit it from the tool bar
and my VPN connection established just fine. I then took
it out of the startup folder so that it wouldn't load when
I started the computer.

However, on all three computers that I have attached
through the MN-700, my VPN connections last for 45
minutes, and then they drop. It's very consistent. One of
them uses a Nortel VPN client and it drops in 45 minutes
also. The internet still works and wireless still works,
but my VPN is kicked.


>-----Original Message-----
>I'm having the same problem but with cisco vpn ... the
>whole thing about the localnet addressing (192.168.*,
>etc) has to do with addressing conflicts between your
>local network and the network you are connecting to ...
>that is they can't have similar subnets ... if the
>destination network actually uses 192.168.1.* internally,
>you'll want to set your router to use 192.168.2.* for
>your home network ... I believe the problem lies
>elsewhere though ... I think it has to do with IPSec
>passthrough ... most sites suggest that you turn off XP's
>ICF (Internet Connection Firewall) or any other similar
>software (ZoneAlarm, etc). I tried that but it didn't do
>anything for me ... I bet the router is the problem ... I
>don't see a setting for IPSec passthrough anywhere ... my
>LinkSys router on the other hand had that option ... the
>more I use my new router the more disappointed I get
>about microsoft's entry into this field ... just another
>example: the router management software is very "fisher
>price" ... and the broadband network utility won't see
>the damn router anymore ... pretty lame. I'll let you
>know if I find anything more useful than just moral
>support. :P
>
>>-----Original Message-----
>>I was able to log into my VPN prior to installng the MN-
>>700, since then it says host is not responding when i
>try
>>to log in. I am running Windows ME. the VPN is Nortel
>>Contivity. I am using cable internet.
>>I did some reading and did one of Barb's suggestions, i
>>changed the IP address in LAN to 192.168.1.1 was that
>>right?? nevertheless it never helped, still got the same
>>message.
>>I'm new to the wireless router kinda thing, so go easy
>on
>>me...lol. Any suggestions would be great, thanks in
>>advance.
>>.
>>
>.
>

I haven't tried the port forwarding thing because
although I have heard of it as well, I just can't find
the specific instructions (what port #, etc) ... I'm
hoping it will allow me to run ICF (XP firewall) once I
take care of the VPN thing ... speaking of which, I'm
still at work and I can't wait to get home and try John
Carse's suggestion (kill that @#$%ing MSBN utility or
whatever it is). I'll let you know if John's suggestion
works but please pass on anything you know on that port-
forwarding thing (I'm guessing it won't do me much good
since I didn't have to specify anything on my linksys
router ... using specious reasoning, it shouldn't help
with ICF either so perhaps I can turn ICF back on without
screwing up anything, ergo the utility app was the
culprit the whole time).

>-----Original Message-----
>The Virtual DMZ works for my laptop only i have XP pro
>there, but on my desktop i tried the DMZ but it booted
me
>out and caused an error, i had to reboot and go through
>scandisk. For the time being I will use DMZ to access my
>VPN. But i was curious, if DMZ makes my network
>susceptable to hackers, how much more of a risk is it
for
>my companies network?? my IT dept. may give me crap if
it
>opens a door for hackers. Or is the companies normal
>protection still there.
>Hey Demetrios did you try the port forwarding idea that
>people were talking about??? I would try it but i don't
>understand it enough to be messing with it.
>>-----Original Message-----
>>I had a similar problem connecting to a client's
network
>that was using the
>>192.168.2.X addressing scheme and the Quest VPN
>software . I resolved my
>>problem by creating a "Virtual DMZ" that pointed back
to
>the IP Address of
>>my laptop. Once I set up the DMZ, I connected almost
>instantly. I kill the
>>Virtual DMZ after each session.
>>
>>"demetrios christopher" <(E-Mail Removed)> wrote
>in message
>>news:149b701c3f8ff$88a85cf0$(E-Mail Removed).. .
>>> I'm having the same problem but with cisco vpn ... the
>>> whole thing about the localnet addressing (192.168.*,
>>> etc) has to do with addressing conflicts between your
>>> local network and the network you are connecting
to ...
>>> that is they can't have similar subnets ... if the
>>> destination network actually uses 192.168.1.*
>internally,
>>> you'll want to set your router to use 192.168.2.* for
>>> your home network ... I believe the problem lies
>>> elsewhere though ... I think it has to do with IPSec
>>> passthrough ... most sites suggest that you turn off
>XP's
>>> ICF (Internet Connection Firewall) or any other
similar
>>> software (ZoneAlarm, etc). I tried that but it
didn't
>do
>>> anything for me ... I bet the router is the
>problem ... I
>>> don't see a setting for IPSec passthrough
anywhere ...
>my
>>> LinkSys router on the other hand had that option ...
>the
>>> more I use my new router the more disappointed I get
>>> about microsoft's entry into this field ... just
>another
>>> example: the router management software is
very "fisher
>>> price" ... and the broadband network utility won't see
>>> the damn router anymore ... pretty lame. I'll let you
>>> know if I find anything more useful than just moral
>>> support. :P
>>>
>>> >-----Original Message-----
>>> >I was able to log into my VPN prior to installng the
>MN-
>>> >700, since then it says host is not responding when i
>>> try
>>> >to log in. I am running Windows ME. the VPN is Nortel
>>> >Contivity. I am using cable internet.
>>> >I did some reading and did one of Barb's
suggestions,
>i
>>> >changed the IP address in LAN to 192.168.1.1 was that
>>> >right?? nevertheless it never helped, still got the
>same
>>> >message.
>>> >I'm new to the wireless router kinda thing, so go
easy
>>> on
>>> >me...lol. Any suggestions would be great, thanks in
>>> >advance.
>>> >.
>>> >
>>
>>
>>.
>>
>.
>

alas, killing the broadband utility (as temporarily cathartic as that was) didn't yield any positive results
back to the drawing board. thanks for setting me up for disappointment though :P