Search:  

 
 
   All ForumsHot TopicsGallery






how-to block ads


 
Forums » Up and Running » Security » Wireless Security » The most secure way to use Windows Remote Desktop
Search Topic:
Share Topic:
RSS topic:
toggle:
flat / full
normal / watch
Posting:
Post a:
Post a:
Is there a way to not see a vulnerable router ? »
AuthorAll Replies

seezar
Premium
join:2001-07-01
Rochester, NY
·ViaTalk


3 edits
reply to Flaubert
Re: The most secure way to use Windows Remote Desk

said by Flaubert See Profile :

So you're saying:
a- Install CopSsh on the server.
b-Install Tunnelier on the client.
c -Forward only port 22 to my private IP ??

Sorry if I seem a little slow but there are a couple of things I need explained:

The parameters you've entered in Tunnelier
under "Host" and "Port"
On the "Login" tab:
I am not on a Domain, so should I just enter my Wan ip on there if I connect from outside my Llan?
On the Options tab:
Do I have to enter the same parameters as yours?

And also, could you be a little more specific on how to create those 2048 bit public/private keys?
I tried reading your openbsd link but I didn't understand it.

Thanks anyway for your help so far. I know a lot more than when I started this thread....
OK, I just set this up and it appears to work very well.

I installed CopSSH on my windows server. CopSSH is pretty cool, its basically OpenSSH with kind of a front end to make it easier to administer. After installing CopSSH I had to go in and 'activate' one of the accounts on the windows server. Once that account is activated I can now SSH to that windows server using that account.

I used PuTTY as a client. I put in the IP of the windows server to connect to. In the tunnel section of PuTTY I put i n a source port of 3390 and a destination of the IP address of the windows server and a destination port of 3389.

So now when I SSH to the windows server, I login with the account I activated. Then I run the remote desktop client. in the connect to box I put in localhost:3390 (3390 was the port I specific as the source). Then I am able to login to the windows server.

So basically, from the outside all you need to do is forward port 22 (or whatever port you are going to SSH to)to the IP of the windows server.

With it setup this way you can go into windows firewall on the server and remove access to remote desktop on port 3389 and make sure you allow access to port 22.

Flaubert

join:2004-12-06
Los Angeles, CA

On the server I have software and hardware firewall.
The hardware part I can take care of by forwarding port 22 to my private ip
Now, will the connection get past Norton Internet Security 2006?
I guess if I enter CopSsh as a legitimate app in the list of trusted apps in NIS 2006 I should be Ok ?!!!
On the client side I will have only software firewall. I guess I will do the same thing for PuTTy.

Now How do I set up those public/private keys....?
Forums » Up and Running » Security » Wireless SecurityIs there a way to not see a vulnerable router ? »


Monday, 23-Nov 15:44:29 Terms of Use | Privacy Policy | Hosting by www.nac.net - DSL,Hosting & Co-lo | feedback | contact
over 10 years online! © 1999-2009 dslreports.com.
page compression OFF
Most commented news this week
· [53] New AT&T Ad Campaign Hits Back At Verizon
· [25] Earthlink Suffers From Major E-mail Outage
· [22] Frontier Increases Modem Rental Fee
· [16] AT&T Offers New Prepaid Wireless plans
· [7] Vivendi In Way Of Comcast's NBC Desires
· [4] Monday Morning Links
Most people now reading
· Getting ready to pull the trigger, still have cold feet. [VOIP Tech Chat]
· Best Bluray player [General Questions]
· Bell's Network Management practices page [TekSavvy]
· Windows 7 boot manager editing questions [Microsoft Help]
· Big Bank Alternative to Bank of America? [General Questions]
· linux box alternative to NetEqualizer ? ? Does it exist? [Wireless Service Providers]
· Extra charge to use Master Card instead of Visa? [General Questions]
· netTalk tk6000 [VOIP Tech Chat]