[OpenAFS] v1.3.6200 on windows fails to start

Derek Atkins warlord@MIT.EDU
Thu, 01 Apr 2004 19:29:12 -0500


How brain-damaged!

Oh well, it's windows.. what should I expect?  a sane OS?

*sighs*

And people VOLUNTARILY run this software?

-derek

Rodney M Dyer <rmdyer@uncc.edu> writes:

> All,
>
> At 06:56 PM 4/1/2004, Derek Atkins wrote:
>>Why don't you just suggest 127.0.0.1?
>
> You can't use that address on a Windows box.  The 127.0.0.1 address is
> a built in loopback address built in to the TCP/IP stack.  This
> loopback address exists even without the MS Loopback virtual network
> adapter installed.
>
> When configuring the MS Loopback virtual network adapter you must
> remember the following on Windows...
>
> 1.  Windows already provides the TCP/IP loopback address 127.0.0.1.
>
> 2.  The MS loopback virtual network adapter will automatically be
> provided the following by Windows routing...
>
>       a.  TCP/IP broadcast resolution.
>       b.  Loopback resolution
>       c.  Network broadcast resolution.
>       d.  Multicast resolution.
>
> In this case your subnet mask must always allow for at least 4
> addresses.  Eg, the rightmost two bits of the mask must always be zero.
>
> 3.  You may also be running some local applications that the loopback
> adapter will interfere with if you set an address that is outside your
> network.  At our site for example, several of our applications are
> licensed.  The license code built in to those applications must think
> they are on the proper subnet.  Some of the applications looked at the
> loopback address instead of the real network card.  In that case the
> software didn't run.  We had to use a loopback address that was within
> our own subnet.
>
> Rodney
>
>
>

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord@MIT.EDU                        PGP key available