[MPICH] MPICH2 on WinXP-Pro cluster

[PETER RAETH]

Many thanks to David for his advice. Following the line of thought he put me 
on I've been able to get things to work. The problem was that, while the 
account names were the same, WinXP-Pro did not have that same name 
throughout its system on the worker node (raethserver). In some places, it 
had a different name. Not sure how that happened since the account manager 
on raethserver showed the correct name. What finally fixed things was to 
delete the account altogether and then re-establish the account. It was not 
necessary to use a hosts or lmhosts file. Nor was it necessary to set up a 
domain server since no domain specification was needed.


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\PROGRA~1\MPICH2\bin>cpi.bat

C:\PROGRA~1\MPICH2\bin>mpiexec -pwdfile Options.txt -exitcodes -hosts 2 
familycomputer raethserver cpi

Enter the number of intervals: (0 quits) 50000
pi is approximately 3.1415926536231167, Error is 0.0000000000333236
wall clock time = 0.004374
Enter the number of intervals: (0 quits) 0
rank: node: exit code
0: familycomputer: 0
1: raethserver: 0

C:\PROGRA~1\MPICH2\bin>


Contents of Options.txt:

  \Peter Raeth
  wickedale



Peter Raeth, Ph.D., Faculty
University of Phoenix (Online Campus)
PeterRaeth at email.uophx.edu
http://www.geocities.com/peter_raeth/


----- Original Message ----- 
From: "David Ashton" <ashton at mcs.anl.gov>
To: "'Peter Raeth (FAC)'" <PeterRaeth at email.uophx.edu>; 
<mpich-discuss at mcs.anl.gov>
Sent: Friday, August 05, 2005 12:15 PM
Subject: RE: [MPICH] MPICH2 on WinXP-Pro cluster


> Peter,
>
> What is the error output?  Can you send us that?
>
> If mpiexec can resolve the ip address of the other machine but cannot
> connect to it then it is probably a firewall issue.  The simple answer is
> that you need to disable the firewall to run MPI applications.
>
> The longer answer is that if you are using the Windows firewall then you 
> can
> configure it to allow the smpd.exe process not to be blocked.  Then you 
> need
> to allow exceptions for each MPI executable that you intend to run.  This
> way you can still have the firewall running but it won't block ports used 
> by
> mpiexec or your application.
>
> -David Ashton
>
> -----Original Message-----
> From: owner-mpich-discuss at mcs.anl.gov
> [mailto:owner-mpich-discuss at mcs.anl.gov] On Behalf Of Peter Raeth (FAC)
> Sent: Friday, August 05, 2005 11:13 AM
> To: 'mpich-discuss at mcs.anl.gov'
> Subject: [MPICH] MPICH2 on WinXP-Pro cluster
>
> This will be an elementary question for most but it has me quite
> roadblocked. Having gone through the entire archive, I could find nothing 
> on
> this particular subject. Thank all in advance for their patience and
> support.
>
> An entry-level cluster is composed of two Intel WinXP-Pro computers
> connected via a cross-over cable. The network is configured such that each
> computer can see shared files and drives on the other machine. The printer
> is shared between the two machines. Each machine can ping the other 
> machine.
> The MPICH2 installer has been run on both machines. Both machines are in 
> the
> same workgroup and one logs onto either in the same way.
>
> When running the very basic example cpi.exe on either machine, cpi works
> just fine. MPIEXEC performs as expected. However, when an attempt is made 
> to
> run across the network, MPIEXEC reports that it can not connect to the 
> other
> machine. It finds the machine but it can not connect to it. It is here 
> that
> I am stuck and would appreciate any advice.
>
> With Linux, everything works really well. We have had no trouble and a lot
> of success.
>
>
> Thanks,
>
> Peter.
>
>