CORRECTION Re: Remote Desktop from Work to Home
From: Tom (anonymous_at_discussions.microsoft.com)
Date: 03/05/04
- Next message: Lanwench [MVP - Exchange]: "Re: XP unable to ping."
- Previous message: Sooner Al: "CORRECTION #2 Re: Remote Desktop from Work to Home"
- In reply to: Sooner Al: "CORRECTION Re: Remote Desktop from Work to Home"
- Next in thread: Sooner Al: "Re: CORRECTION Re: Remote Desktop from Work to Home"
- Reply: Sooner Al: "Re: CORRECTION Re: Remote Desktop from Work to Home"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 5 Mar 2004 06:49:35 -0800
That's me too, they told me to try this group, There must
be a setting somewhere on the router that I'm not
checking, what about DMZ? would that do the trick?
>-----Original Message-----
>Belay that... The correct news server address is...
>
>news://msnews.microsoft.com/microsoft.public.broadband.net
.hardware
>
>Sorry about that...
>
>--
> Al Jarvi (MS-MVP Windows Networking)
>
>Please post *ALL* questions and replies to the news group
for the mutual benefit of all of us...
>The MS-MVP Program - http://mvp.support.microsoft.com
>This posting is provided "AS IS" with no warranties, and
confers no rights...
>
>"Sooner Al" <SoonerAl@somewhere.net.invalid> wrote in
message
>news:u9Wrh1rAEHA.3308@TK2MSFTNGP10.phx.gbl...
>> Additionally, here is long thread concerning the same
issue from another user on the
>>
news://msnews.micosoft.com/microsoft.public.broadbandnet.ha
rdware news group...
>>
>>
>http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-
8&frame=right&th=224db61fc5d187ce&seekm=2c3e01c3e149%
24032b2fd0%24a501280a%40phx.gbl#link1
>>
>> --
>> Al Jarvi (MS-MVP Windows Networking)
>>
>> Please post *ALL* questions and replies to the news
group for the mutual benefit of all of us...
>> The MS-MVP Program - http://mvp.support.microsoft.com
>> This posting is provided "AS IS" with no warranties,
and confers no rights...
>>
>> "Sooner Al" <SoonerAl@somewhere.net.invalid> wrote in
message
>> news:eZ$0HxrAEHA.576@TK2MSFTNGP11.phx.gbl...
>> > If the telnet test fails then its probably a router
issue, particularly since you can connect
>> > internally on your home LAN. Obviously TCP Port 3389
is not blocked outbound by your work
>network
>> > administrators and your ISP does not block TCP Port
3389 inbound (highly unlikely anyway) since
>> you
>> > coworker can RD to his home.
>> >
>> > Are you?
>> >
>> > 1. Running the latest firmware on the MN-620 router?
>> > 2. Sure, double sure, triple sure...sure that you
have the MN-620 router configured correctly
>for
>> > port forwarding?
>> > 3. Sure, double sure, triple sure...sure that you are
calling the correct public IP for your
>> router?
>> >
>> > Anyway to temporarily borrow a friends router, ie. of
a different manufacturer and/or model, to
>> > test?
>> >
>> > --
>> > Al Jarvi (MS-MVP Windows Networking)
>> >
>> > Please post *ALL* questions and replies to the news
group for the mutual benefit of all of us...
>> > The MS-MVP Program - http://mvp.support.microsoft.com
>> > This posting is provided "AS IS" with no warranties,
and confers no rights...
>> >
>> > "Tom" <anonymous@discussions.microsoft.com> wrote in
message
>> > news:A8C7BAF4-4BA2-4898-A676-
A11EB20886C4@microsoft.com...
>> > > Tried the telnet test, didn't work, I can remote
desktop to my other pcs in the LAN but not
>from
>> > work, I can ping from work to my home pc no problem,
also another guy here at work has the same
>> ISP
>> > and he can use Remote Desktop from here, the only
difference is I have a Microsoft router he has
>a
>> > different router. Any other suggestions?
>> > >
>> > > ----- Sooner Al wrote: -----
>> > >
>> > > Well, presuming you can open and forward ports
through your MN-620 then you might try
>this
>> > telnet
>> > > test to see if you can pinpoint the problem
area...
>> > >
>> > > http://support.microsoft.com/default.aspx?
scid=kb;en-us;Q187628
>> > >
>> > > Call using the public IP of the router.
>> > >
>> > > Can you test Remote Desktop access on your
local home LAN to make sure it works? That
>would
>> > narrow
>> > > down the problem to the router or perhaps TCP
Port 3389 being blocked outbound by your
>work
>> > > network...
>> > >
>> > > FYI, I just looked at the users manual for the
MN-620 (which downloaded from MS) and
>could
>> > not find
>> > > anything concerning port forwarding.
>> > > --
>> > > Al Jarvi (MS-MVP Windows Networking)
>> > >
>> > > Please post *ALL* questions and replies to the
news group for the mutual benefit of all
>of
>> > us...
>> > > The MS-MVP Program -
http://mvp.support.microsoft.com
>> > > This posting is provided "AS IS" with no
warranties, and confers no rights...
>> > >
>> > > "Tom" <anonymous@discussions.microsoft.com>
wrote in message
>> > > news:6fac01c40226$3bfb1520$a301280a@phx.gbl...
>> > > > I can't get my MN-620 router to let me
connect from my
>> > > > work network to my home network, I can ping
my pc at home
>> > > > no problem and I can do a tracert too,
nslookup works fine
>> > > > also, I have all the ports open, etc. any
suggestions
>> > > >> Thanks
>> > >
>> > >
>> >
>>
>
>.
>
- Next message: Lanwench [MVP - Exchange]: "Re: XP unable to ping."
- Previous message: Sooner Al: "CORRECTION #2 Re: Remote Desktop from Work to Home"
- In reply to: Sooner Al: "CORRECTION Re: Remote Desktop from Work to Home"
- Next in thread: Sooner Al: "Re: CORRECTION Re: Remote Desktop from Work to Home"
- Reply: Sooner Al: "Re: CORRECTION Re: Remote Desktop from Work to Home"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
