Using DRAC 4 card behind a firewall/router - consol redirect fails

Well, Steve, as far as I know, the admin server is looking for the correct IP address. If I remember correctly, your AdminClientPC sends packets to the address 192.168.1.10 but with the destination MAC address of your local gateway, which is 192.168.1.10.

Now, I am not sure how you have your network setup with subnet masks, but the description you gave me below will not work in the traditional sense, simply because your AdminClientPC assumes that the DRAC4 is in the same subnet and not in another subnet, causing the adminclientPC to route packets to the gateway, instead of broadcasting them onto the network. So, you should setup your network something like this:

AdminClientPC------->>>>Router/FW1<<<---------->>>>Router/FW1<<<--------->>>>Drac4-Server
(192.168.2.200)___(192.168.2.10)(65.65.65.20)___(65.65.65.63)_(192.168.1.1)____(192.168.1.10)

This way, the admin client PC assumes that anything with the 192.168.1.x subnet is outside it's local network, so it will route the packet to the Router/FW1, and the Router/FW1 will handle the rest of it.

Also, I dont know if you are doing any NAT on either of your Router/FW1s, but that can cause problems with the packets too.

Saunders

Message Edited by SaundersR on 01-10-2005 06:08 PM

I have the same problem, my Server is behind a firewall and has a NAT'd address, I have all the required ports opened but when I initiate a console redirection the Java Applet tries to use the local address of the DRAC and not the NAT address.

ie, I connect the web browser to the 192.85.29.87 (the NAT address), the Java console tries to open on 10.1.8.33 (DRAC address).

Any way to force the Java console to use the NAT address ?

Hi guys,

I have discovered a way to work around this problem for the time being. Basically, the problem boils down to bad programming on the DRAC (the java applet tries to use the internal address of the drac itself, as opposed to the HTTP host header when it tries to connect).

Here's how I work around the problem.

1. If your local PC is using a dynamic address, change it to a static address temporarily-- so, if you run ipconfig /all, and you have an assigned address from DHCP of 10.0.1.100, mask 255.255.255.0, gw 10.0.1.1, (for example, use the information relevant to your configuration) etc... write these numbers down, and change your PC to have a static address based on what DHCP previously assigned you. (You need to have a static address in order to add a secondary static address in step 2)

2. From the DRAC configuration, find out *exactly* what the DRAC IP is. Mine, for example is 192.168.0.2. Take this address, and give your local machine a *second ip* of this same address by going into the advanced properties of TCP/IP (use a 255.255.255.0 or smaller subnet mask). So now, your machine has 2 static addresses (based on this example): 10.0.1.100, and 192.168.0.2

3. Download TCP Redirector at http://hp.vector.co.jp/authors/VA005851/soft/tcp-redirector/index-eng.html

4. Decompress the file using WinRAR (or some other compatible file decompression utility) and run the execuatble inside. Tell it to redirect TCP port 5900 to whatever the *external* IP is for your DRAC (this is the public address of your NAT or router device that your drac is behind). Press "start" on the utility.

5. Log into the DRAC web interface and attempt to connect to the console. When you attempt to connect to the console, what will now happen is that the virtual KVM java applet from the DRAC will end up trying to connect to your *local* machine, and the TCP redirector will redirect the traffic to the DRAC.

Dimitri,

Good work, works a treat :smileyhappy:

Would still prefer Dell to update the JavaApp though, i mean, how hard can it be ...

Thanks for the post - FINALLY!  How or from whom at Dell can we get this BETA version?

Steve