WebSphere Addnode fails with connection timeout during federation

Environment:
1.)StandAlone App server on Windows
2.)DMGR on Linux
3.)WAS 7.0

While trying to federate a standalone node from Windows to Linux using 'Addnode' command from the appsrv profile of Windows,It was failing with the following error:

ADMU0009I: Successfully connected to Deployment Manager Server:
node.name.extension:8879
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: server1
ADMU2010I: Stopping all server processes for node serverNameNode01
ADMU0512I: Server server1 cannot be reached. It appears to be stopped.
ADMU0512I: Server server1 cannot be reached. It appears to be stopped.
ADMU0024I: Deleting the old backup directory.
ADMU0015I: Backing up the original cell repository.
ADMU0012I: Creating Node Agent configuration for node: serverNameNode01
ADMU0014I: Adding node serverNameNode01 configuration to cell:serverNameCell01
ADMU0027E: An error occurred during federation Connection timed out: connect;
rolling back to original configuration.
ADMU0211I: Error details may be seen in the file:
C:\IBM\WebSphere\AppServer\profiles\AppSrv03\logs\addNode.log
ADMU0026I: An error occurred during federation; rolling back to original
configuration.
ADMU0113E: Program exiting with error:
com.ibm.websphere.management.exception.AdminException:
com.ibm.websphere.management.filetransfer.client.TransferFailedException:
Upload retry limit exceeded for file
C:\DOCUME~1\Admin\LOCALS~1\Temp\2\serverNameNode01__1751832905898309717.car
Exception: java.net.ConnectException: Connection timed out: connect,
resulting from: java.net.ConnectException: Connection timed out:
connect
ADMU1211I: To obtain a full trace of the failure, use the -trace option.
ADMU0211I: Error details may be seen in the file:
C:\IBM\WebSphere\wp_profile\logs\addNode.log
Target finished: action-cluster-node-federation
Target finished: cluster-node-config-pre-federation

How did I resolve?:
---------------------
While googling found a useful link,
http://www-01.ibm.com/support/docview.wss?uid=swg21395448

Based on that made sure,There are'nt multiple IP addresses on the Linux box (Where my DMGR is hosted)

So far,I was trying to federate using IP address,Something like,
addnode 192.168.1.7 8879 -includeapps

That was the mistake,With addnode use only 'hostname' when DMGR resides on another physical mistake.
Added '192.168.1.7' to my hosts file on windows.Something like:

192.168.1.7 fedex   (File located: C:\WINDOWS\system32\drivers\etc\hosts)

That was it,This time I started using hostname Instead of IP

addnode fedex 8879 -includeapps