%WINDIR%\SYSTEM32\DRIVERS\ETC\HOSTS
You could always run your own name server on one of your Linux systems 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 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.
Anyone know a fix or work-around for this?
Rich
_______________________________________________
OpenAFS-info mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-info
smime.p7s
Description: S/MIME Cryptographic Signature
