[OpenAFS] Connection problems in different networking environments

Jonathan Brandmeyer Jonathan Brandmeyer" <jbrand_235@earthlink.net
Fri, 27 Sep 2002 21:56:40 -0400


This is a multi-part message in MIME format.

------=_NextPart_000_000B_01C26670.C2A8FC20
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

System conditions:
WinXP Pro,
Open AFS for Windows v 1.2.2b
MIT Kerberos for Windows 2.1.1

I use the Leash32 application to obtain afs tokens.  Leash automatically =
does the buisiness of running k524init to convert v5 tgt to v4 tgt and =
also generates afs tokens.  I have to start the AFS client first, then =
run Leash32.

Under the following conditions I authenticate and mount successfully:
Connected to a home LAN using a 192.168.x.x address, Internet =
communication is obtained through NAT to a public IP.  My computer sees =
only the IP of the local gateway for DNS and default gateway.  Leash32 =
reports that my Domain Name is some kind of garbage list of symbols =
(probably just doesn't exist).

Under these conditions, I cannot start the AFS client, but Leash32 =
successfully obtains v5 and v4 tgt's:
Connected to a campus LAN, assigned IP of 152.7.x.x.  The default =
gateway and DNS servers are all different addresses on the campus =
network (152.7.x.x).  Leash32 reports that my Domain Name is =
nomadic.ncsu.edu.  The only way that I can start the service (on =
campus)is if I configure afs to not map any network drives or global =
drives.  Any attempt to subsequently map afs locations (including the =
global /afs )fails.

What kinds of network communication would totally prevent me from =
starting the service under one set of conditions and not another?  Is =
there a configuration change I can make to work around it, or is it =
soley on the gateway/dns servers' end?

I appreciate any assistance ya'll can provide.
------=_NextPart_000_000B_01C26670.C2A8FC20
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>System conditions:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>WinXP Pro,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Open AFS for Windows v =
1.2.2b</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>MIT Kerberos for Windows =
2.1.1</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I use the Leash32 application to obtain =
afs=20
tokens.&nbsp; Leash automatically does the buisiness of running k524init =
to=20
convert v5 tgt to v4 tgt and also generates afs tokens.&nbsp; I have to =
start=20
the AFS client first, then run Leash32.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Under the following conditions =
I&nbsp;authenticate=20
and mount&nbsp;successfully:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Connected to a home LAN using a =
192.168.x.x=20
address, Internet communication is obtained through NAT to a public =
IP.&nbsp; My=20
computer sees only the IP of the local gateway for DNS and default=20
gateway.&nbsp; Leash32 reports that my Domain Name is some kind of =
garbage list=20
of symbols (probably just doesn't exist).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Under these conditions, I cannot start =
the AFS=20
client, but Leash32 successfully obtains v5 and v4 tgt's:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Connected to a campus LAN, assigned IP =
of=20
152.7.x.x.&nbsp; The default gateway and DNS servers are all different =
addresses=20
on the campus network (152.7.x.x).&nbsp; Leash32 reports that my Domain =
Name is=20
nomadic.ncsu.edu.&nbsp; The only way that I can start the service (on =
campus)is=20
if I configure afs to not map any&nbsp;network drives or global =
drives.&nbsp;=20
Any attempt to subsequently map afs locations (including the global /afs =

)fails.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>What kinds of =
network&nbsp;communication would=20
totally prevent me from starting the service under one set of conditions =
and not=20
another?&nbsp; Is there a configuration change I can make to work around =
it, or=20
is it soley on the&nbsp;gateway/dns servers'&nbsp;end?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I appreciate any assistance ya'll can=20
provide.</FONT></DIV></BODY></HTML>

------=_NextPart_000_000B_01C26670.C2A8FC20--