|
Home > Archive > alt.certification.network-plus > April 2005 > Remote Desktop and FTP Problem
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Remote Desktop and FTP Problem
|
|
|
| I'm stuck.
I had a successful RD and FTP connection from my work computer going
into my Linksys router at home, into my home network. Recently, the OS
on my main box at home corrupted, and I restored it with a Ghost image
that was about 4 months old. Now, no RD, or FTP for that matter.
Here's the odd thing. I can use RD on my other home box to get to the
main box when I use its internal (192.168.x.x) address, but no luck on
the outside the router.
I have made no changes to the router config. Port 3389 and 21 still
forward to my main box, and my main box allows me as an administrator to
have remote access. Any ideas? I've rebooted the router, cable modem,
released and renewed the IP on the main box, router and modem. Made
sure the remote services were going, and disabled the software firewalls
for troubleshooting.
Thanks.
| |
| el Diablo 2005-04-06, 2:46 pm |
| Can you still get through from work? Try NMap (NMapWin for M$ users) to
check if the ports are really open to the outside. Your ISP for the
house could have block traffic on those ports or the ISP for work could
have blocked it. NMap will tell you.
Other than that sounds like some kind of configuration issue that you
may have made four months ago, but forgot to note.
Bundy wrote:
> I'm stuck.
>
> I had a successful RD and FTP connection from my work computer going
> into my Linksys router at home, into my home network. Recently, the OS
> on my main box at home corrupted, and I restored it with a Ghost image
> that was about 4 months old. Now, no RD, or FTP for that matter. Here's
> the odd thing. I can use RD on my other home box to get to the main
> box when I use its internal (192.168.x.x) address, but no luck on the
> outside the router.
> I have made no changes to the router config. Port 3389 and 21 still
> forward to my main box, and my main box allows me as an administrator to
> have remote access. Any ideas? I've rebooted the router, cable modem,
> released and renewed the IP on the main box, router and modem. Made
> sure the remote services were going, and disabled the software firewalls
> for troubleshooting.
>
> Thanks.
| |
|
| el Diablo wrote:
[color=blue]
> Can you still get through from work? Try NMap (NMapWin for M$ users) to
> check if the ports are really open to the outside. Your ISP for the
> house could have block traffic on those ports or the ISP for work could
> have blocked it. NMap will tell you.
>
> Other than that sounds like some kind of configuration issue that you
> may have made four months ago, but forgot to note.
>
> Bundy wrote:
>
That's an idea. LAN admin recently installed WebSense. Does that
program have the ability to block those ports? I'm trying to use
terminal services to get to the home network, if that helps.
Thanks,
Bundy
| |
| el Diablo 2005-04-06, 2:46 pm |
| I just took a quick look at what Websense is/does and it appears that
you need to check to see if it is filtering out your comms with box at home.
Of course, you can probably find that out yourself if you use NMap at
work and check what ports can get out/in. Remember to specify your ip on
the outside.
Bundy wrote:
> el Diablo wrote:
>
>
>
> That's an idea. LAN admin recently installed WebSense. Does that
> program have the ability to block those ports? I'm trying to use
> terminal services to get to the home network, if that helps.
>
> Thanks,
>
> Bundy
| |
|
| el Diablo wrote:
[color=blue]
> I just took a quick look at what Websense is/does and it appears that
> you need to check to see if it is filtering out your comms with box at
> home.
>
> Of course, you can probably find that out yourself if you use NMap at
> work and check what ports can get out/in. Remember to specify your ip on
> the outside.
>
> Bundy wrote:
>
<snip>
Just used NMap, and you're right. 3389 and 21 aren't showing up; only
mail and web ports. Great catch, and thanks for your help. Now I have
to figure out a way around that. ;-)
Bundy
| |
|
| You're going to have to open those ports through the Websense.
AG
"Bundy" <bundy@caribou.com> wrote in message
news:avVfd.3452077$ic1.351751@news.easynews.com...
> el Diablo wrote:
>
> <snip>
>
> Just used NMap, and you're right. 3389 and 21 aren't showing up; only
> mail and web ports. Great catch, and thanks for your help. Now I have to
> figure out a way around that. ;-)
>
> Bundy
| |
|
| AG wrote:
> You're going to have to open those ports through the Websense.
>
> AG
> "Bundy" <bundy@caribou.com> wrote in message
> news:avVfd.3452077$ic1.351751@news.easynews.com...
>
>
>
>
Shoot. Net admin has the only access. Thanks for the info.
| |
|
|
"Bundy" <bundy@caribou.com> wrote in message
news:Nxtgd.4147048$6p.690781@news.easynews.com...
> AG wrote:
> Shoot. Net admin has the only access. Thanks for the info.
Yeah we admins are that way. :-)
AG
|
|
|
|
|