Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | RE: Remote Desktop, DMZ |
|---|---|
| Date: | Wed, 25 Apr 2007 16:39:57 -0500 |
Ed, A remote accessible system such as Windows Server 2003 with remote desktop enabled is an easy way to get access like you describe. Here we have VPN clients connect from the internet to a DMZ where our remote access system is located. This system (Server 2003) is not on the domain. After connecting to the system users then have to connect from the DMZ to LAN on TCP/3389 since we are using Windows remote desktop. For you to get access to your application server you also simply should be able to allow access on the port(s) required. Nick Vaernhoej "Quidquid latine dictum sit, altum sonatur." -----Original Message----- From: listbounce@securityfocus.com [mailto:listbounce@securityfocus.com] On Behalf Of Edmund Sent: Tuesday, April 24, 2007 6:16 AM To: security-basics@securityfocus.com Subject: Remote Desktop, DMZ Dear All, A Remote-Desktop system should be placed within the DMZ, am I correct? If that is the case, what if the Remote Desktop system requires access to an application server; but, this application server cannot be placed in the DMZ because LAN users also need access to it? I've been mulling it over and haven't quite figured out how or where to put this remote desktop system. In the DMZ, it will have a hard time being part of the domain(is this actually necessary?) or even access an application server (which is also part of the domain). If I put the Remote desktop system in the internal LAN, the risks are not particularly appealing should the RD system get compromised. Can someone out there give me some hints/pointers as to how I might go about in putting a remote desktop system in an existing network setting? Thanks Ed This electronic transmission is intended for the addressee (s) named above. It contains information that is privileged, confidential, or otherwise protected from use and disclosure. If you are not the intended recipient you are hereby notified that any review, disclosure, copy, or dissemination of this transmission or the taking of any action in reliance on its contents, or other use is strictly prohibited. If you have received this transmission in error, please notify the sender that this message was received in error and then delete this message. Thank you.
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: Remote Desktop, DMZ, Navroz Shariff |
|---|---|
| Next by Date: | Re: Identifying Intrusions?, fskrc1 |
| Previous by Thread: | RE: Remote Desktop, DMZ, Navroz Shariff |
| Next by Thread: | Re: Remote Desktop, DMZ, Ansgar -59cobalt- Wiechers |
| Indexes: | [Date] [Thread] [Top] [All Lists] |