<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:s="http://www.techrepublic.com/search" xmlns:dc="http://purl.org/dc/elements/1.1/"  xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
    <title><![CDATA[Discussion on What you need to know about the Dell DRAC ]]></title>
    <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-249879]]></link>
    <atom:link rel="hub" type="application/rss+xml" href="http://pubsubhubbub.appspot.com/" />
    <atom:link rel="self" type="application/rss+xml" href="http://www.techrepublic.com/forum/discussions/102-249879/rss" />

    <description><![CDATA[]]></description>
    <language>en-us</language>
    <lastBuildDate>2013-05-25T15:29:34-07:00</lastBuildDate>
             

    <item>
        <title><![CDATA[RE: What you need to know about the Dell DRAC]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-249879-2642036]]></link>
        <description><![CDATA[Does anyone know how to get the graphical remote console to work via the ERA port on the PE2650?  Every time I try to access via Remote Access &gt; Console Redirect my console client goes blank and the message &quot;Warning: Remote Console Not Available&quot; appears at the bottom.  Please see system details below:PowerEdge 2650 BIOS A19OMSA 5.4.0DRAC Version 3.14Dell Embedded Remote Access (ERA)Version 3.38Any advise or assistance that anyone could provide would greatly appreciated.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-249879-2642036]]></guid>
        <dc:creator><![CDATA[anitra.davis@...]]></dc:creator>
        <pubDate>Tue, 18 Nov 2008 11:59:58 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Not Really]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-249879-2400741]]></link>
        <description><![CDATA[I'd just recommend super complex passwords.  One practice I came across was for DRAC and iLO type interfaces is to disable the LAN port on your managed switch except when it is specifically required.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-249879-2400741]]></guid>
        <dc:creator><![CDATA[b4real@...]]></dc:creator>
        <pubDate>Fri, 11 Jan 2008 10:57:11 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[I know...]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-249879-2400740]]></link>
        <description><![CDATA[Yeah I know, but I don't like that as it is then less separate from the OS.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-249879-2400740]]></guid>
        <dc:creator><![CDATA[b4real@...]]></dc:creator>
        <pubDate>Fri, 11 Jan 2008 10:54:47 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Missed a big feature]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-249879-2397956]]></link>
        <description><![CDATA[With the DRAC 5 series, the card can share NICs with the server, and also do vlan tagging.  This has two benefits: connectivity to the DRAC can fail over from one nic to the other in a high-availability installation, and your switch port count is reduced.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-249879-2397956]]></guid>
        <dc:creator><![CDATA[icedivr@...]]></dc:creator>
        <pubDate>Tue, 08 Jan 2008 10:52:55 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[pretty low risk]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-249879-2397955]]></link>
        <description><![CDATA[From the server, you can configure the DRAC card with a commmand-line application, but to use the card, you have to be able to route traffic to it, as if it were another device on the network.  As long as machines in the DMZ can't do that, you're ok.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-249879-2397955]]></guid>
        <dc:creator><![CDATA[icedivr@...]]></dc:creator>
        <pubDate>Tue, 08 Jan 2008 10:45:04 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[review papers for you]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-249879-2397428]]></link>
        <description><![CDATA[Hi MandmsThere are always risks concerned with anything that you have to access remotley, however here is a couple of links to help you understand the DRAC and how you can manage the risks.DRAC 4DRAC 5http://www.dell.com/downloads/global/solutions/DellRemoteAccessController4Security.Pdfhttp://www.dell.com/downloads/global/solutions/DellRemoteAccessController5Security.Pdf]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-249879-2397428]]></guid>
        <dc:creator><![CDATA[GuardianOZ]]></dc:creator>
        <pubDate>Mon, 07 Jan 2008 15:53:26 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Security Concerns]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-249879-2397235]]></link>
        <description><![CDATA[Are there any security concerns I should have of a hacker somehow gaining access to the DRAC and having a back door entrance into our internal network. For example, let's say I have a public web server in a DMZ. I then configure and connect a DRAC directly into my internal network for management. Would there be any way for a hacker, connecting to the web server from the outside, to somehow use the DRAC to gain direct access into our internal network?]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-249879-2397235]]></guid>
        <dc:creator><![CDATA[mandms7]]></dc:creator>
        <pubDate>Mon, 07 Jan 2008 11:00:55 -0800</pubDate>
    </item>
    </channel>
</rss>

