[OpenAFS] Windows Client Won't Accept VL Server Address

[Eggert, Richard W, II (Rich), GVSOL]

This is a multi-part message in MIME format.

------_=_NextPart_001_01C38C32.9EFE2CCC
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Okay, that fixed that problem.

However, now it tells me that the authentication server is unavailable =
when I try to log in.    I'm able to log in just fine on my Linux =
machines.


Rich Eggert
Senior Technical Associate 2
Technology Leadership Program 2
AT&T Government Solutions


-----Original Message-----
From: Jeffrey Altman [mailto:jaltman@columbia.edu]
Sent: Monday, October 06, 2003 8:51 AM
To: Richard Eggert II
Cc: openafs-info@openafs.org
Subject: Re: [OpenAFS] Windows Client Won't Accept VL Server Address


The hosts file on Windows is located at

  %WINDIR%\SYSTEM32\DRIVERS\ETC\HOSTS

You could always run your own name server on one of your Linux systems=20
and configure Windows to rely on Linux for DNS.

Jeffrey Altman


Richard Eggert II wrote:

>My single-server AFS cell is now playing nicely with clients running =
Red Hat
>Linux.
>
>However, the Windows client refuses to behave.
>
>Here's the scenario:
>
>192.168.1.100, privately known as "whiskey.richard_eggert.comcast.net"
>running Red Hat Linux 8 (dual booted with Windows 2000 Pro, not yet
>configured for AFS) - AFS client works fine
>
>192.168.1.102, privately known as "pilsner", but not yet added to =
static
>name mappings on other machines
>running Windows XP Pro - AFS client not functioning
>
>192.168.1.103, privately known as "vodka.richard_eggert.comcast.net"
>running Red Hat Linux 9=20
>designated AFS server
>AFS client works fine
>
>
>Since I don't have my own name server, I have to rely on the /etc/hosts
>files on the Linux machines to provide mappings for the private =
hostnames.
>I have no idea of how to provide such mappings in Windows, if it's even
>possible.
>
>When I try to specify a VL server for my cell on the Windows client, I =
enter
>the name of the server as is listed above and provide the IP address, =
but it
>gives me the message, "Windows could not find a network address for
>192.168.1.103.  Check to make sure you typed the name of the machine
>correctly."  It absolutely refuses to just accept the settings as-is.=20
>
>Anyone know a fix or work-around for this?
>
>
>
>Rich
>
>
>_______________________________________________
>OpenAFS-info mailing list
>OpenAFS-info@openafs.org
>https://lists.openafs.org/mailman/listinfo/openafs-info
> =20
>

------_=_NextPart_001_01C38C32.9EFE2CCC
Content-Type: text/x-vcard;
	name="Richard (Rich) W Eggert II SOLGV (E-mail).vcf"
Content-Transfer-Encoding: base64
Content-Description: Richard (Rich) W Eggert II SOLGV (E-mail).vcf
Content-Disposition: attachment;
	filename="Richard (Rich) W Eggert II SOLGV (E-mail).vcf"

QkVHSU46VkNBUkQNClZFUlNJT046Mi4xDQpOOkVnZ2VydDtSaWNoYXJkIChSaWNoKTs7O0lJIFNP
TEdWDQpGTjpSaWNoYXJkIChSaWNoKSBXIEVnZ2VydCBJSSBTT0xHViAoRS1tYWlsKQ0KT1JHOkJF
IChCRSAtIEFUJlQgQlMgU1ZDUyBFTlRFUlBSSVNFKTtTT0xHViAoQlNFLUdWUk5NTlQgU09MIC0g
RkVERVJBTCkNClRJVExFOlNFTklPUiBURUNITklDQUwgQVNTT0NJQVRFIElJDQpURUw7V09SSztW
T0lDRTorMSA0NDMgMjU5LTM4NDcNClRFTDtDRUxMO1ZPSUNFOisxIDYwOSAzNTEtNjg3Nw0KQURS
O1dPUks6Ozs3MTI1IENPTFVNQklBIEdBVEVXQVkgRFI7Q09MVU1CSUE7TUQ7MjEwNDYtMDAwMDtV
TklURUQgU1RBVEVTDQpMQUJFTDtXT1JLO0VOQ09ESU5HPVFVT1RFRC1QUklOVEFCTEU6NzEyNSBD
T0xVTUJJQSBHQVRFV0FZIERSPTBEPTBBQ09MVU1CSUEsIE1EIDIxMDQ2LTAwMDA9MEQ9MEFVTklU
RUQgU1RBVEVTDQpFTUFJTDtQUkVGO0lOVEVSTkVUOnJ3ZWdnZXJ0QGF0dC5jb20NClJFVjoyMDAz
MDgxMVQxOTA1MDBaDQpFTkQ6VkNBUkQNCg==

------_=_NextPart_001_01C38C32.9EFE2CCC--