G
Guest
Guest
Archived from groups: microsoft.public.broadbandnet.hardware (More info?)
Hi to all those following this thread.
Guess what? I figured it out!
On Microsoft's own Knowledge Base they suggest using Port
Forwarding. They tell you to use 1024-65535 TCP for
Client Ports and 1723 TCP for a Server Port. The first
one made no sense because on Contivity you can only
configure a maximum range of 100 ports. So instead of
trying to configure the full range I just configured port
1024 and 65535.
This alone did not work. But when I then also engaged DMZ
bingo!
I hate the thought of using DMZ. It is like leaving your
front door open when you go to work in the morning. But
it seems this is the only way to access my work network
without disconnecting the MN-700 router.
Hope this helps some other hapless victims of this obtuse
procedure. Microsoft needs to address this flaw in their
hardware. It shouldn't take more than six months of trial
and error to figure this out.
Hi to all those following this thread.
Guess what? I figured it out!
On Microsoft's own Knowledge Base they suggest using Port
Forwarding. They tell you to use 1024-65535 TCP for
Client Ports and 1723 TCP for a Server Port. The first
one made no sense because on Contivity you can only
configure a maximum range of 100 ports. So instead of
trying to configure the full range I just configured port
1024 and 65535.
This alone did not work. But when I then also engaged DMZ
bingo!
I hate the thought of using DMZ. It is like leaving your
front door open when you go to work in the morning. But
it seems this is the only way to access my work network
without disconnecting the MN-700 router.
Hope this helps some other hapless victims of this obtuse
procedure. Microsoft needs to address this flaw in their
hardware. It shouldn't take more than six months of trial
and error to figure this out.