Hi Jeff, where in the client source is the drive mapping done ?
thanks, Ron >Then I don't think your problem is related because Allen's problem >is the fact that his servers are multi-homed and his clients do >not reliably find the correct IP address. > >You have already narrowed your problem down to something related >to the Network Drive mapping configuration. That is where additional >time will have to be spent. > > > >Ron Croonenberg wrote: >> Uhm.. multi-homed as in having multiple ip addresses ? nope. >> The machine has 3 ethernet cards, but 2 of them are not activated on startup. >> >> Ron >> >> >> >>>I think Allen Moy is trying to explain to you what might be wrong >>>with your servers as visible from your Windows client. Is your >>>new server multihomed? >>> >>>Jeffrey Altman >>> >>> >>>Ron Croonenberg wrote: >>> >>> >>>>Apparently there's someone who experienced similar problems with windows >> >> clients >> >>>>and a second afs server/cell. >>>> >>>>I attached the msg.... >>>> >>>> >>>>any ideas or comments ? >>>> >>>>thanks, >>>> >>>>Ron >>>>================================================================= >>>>1879: >>>> Thomas Edison gets an idea, and his brother Timmy says, >>>> "Hey, what's that thing over your head? >>>>================================================================= >>>> Ron Croonenberg | Phone: 1 765 658 4761 >>>> Technology Coordinator | Fax: 1 765 658 4732 >>>> | >>>> Department of ComputerScience | e-mail : [EMAIL PROTECTED] >>>> DePauw University | >>>> Julian Science & Math Center | >>>> 602 South College Ave. | >>>> Greencastle, IN 46135 | >>>>================================================================= >>>> http://www.depauw.edu/acad/computer/RonCroonenberg.asp >>>>================================================================= >>>> >>>> >>>>------------------------------------------------------------------------ >>>> >>>>MIME-Version: 1.0 >>>>Content-Type: Message/rfc822 >>>> >>>>Return-path: <[EMAIL PROTECTED]> >>>>Received: from barracuda.depauw.edu >>>> (SURFCONTROL.depauw.edu [163.120.7.24]) >>>> by depauw.edu; Tue, 12 Oct 2004 08:57:30 -0500 >>>>Received: from maz015.math.ust.hk (maz015.math.ust.hk [143.89.17.15]) >>>> by barracuda.depauw.edu (Spam Firewall) with SMTP id 4A4B8D000095 >>>> for <[EMAIL PROTECTED]>; Tue, 12 Oct 2004 09:00:27 -0500 (EST) >>>>Received: from moy (helo=localhost) >>>> by maz015.math.ust.hk with local-esmtp (Exim 3.36 #1 (Debian)) >>>> id 1CHNCJ-0000RL-00; Tue, 12 Oct 2004 22:00:15 +0800 >>>>Date: Tue, 12 Oct 2004 22:00:15 +0800 (HKT) >>>>From: Allen Moy <[EMAIL PROTECTED]> >>>>To: [EMAIL PROTECTED] >>>>Subject: your OpenAFS posting >>>>Message-ID: <[EMAIL PROTECTED]> >>>>MIME-Version: 1.0 >>>>Content-Type: TEXT/PLAIN; charset=US-ASCII >>>>X-Virus-Scanned: by Barracuda Spam Firewall at depauw.edu >>>> >>>> >>>>I found, by google, your posting >>>> >>>> [OpenAFS] still problem with windows client >>>> >>>>I recently setup, for the first time, an afs >>>>fileserver on a Linux machine running debian. >>>>The afs cell can be accessed from Linux and Windows >>>>clients. When I repeated the installation process >>>>on a second machine to solidify my new knowledge, >>>>I discovered that the 2nd afs cell was accessible >>>>from Linux clients, but not accessible from Windows >>>>clients. >>>> >>>>After much confusion, I realized that both machines >>>>had two IP numbers (for internal and external networks). >>>>In the case of the 1st machine, the external IP number >>>>is assigned to eth0, and the afs fileserver is assigned >>>>to this IP number. In the 2nd case, the external IP number >>>>is assigned to eth1, and so is the afs fileserver. >>>> >>>>When I did a >>>> vos examine root.cell >>>>on the properly working 1st machine, it showed the root.cell >>>>had an assigned machine name which matched the external >>>>machine name on eth0. >>>> >>>>The same >>>> vos examine root.cell >>>>on the 2nd machine showed the root.cell to be assigned to >>>>the machine name of the internal interface eth0. >>>> >>>>On the troubled 2nd machine, I edited files to turn off >>>>the configuration of eth0 at boot, and then reboot. >>>>After reboot, >>>> vos examine root.cell >>>>showed an assignment of root.cell to the machine name of >>>>the external eth1 interface. Most importantly, Windows >>>>client access started working. >>>> >>>>If your troubled afs fileserver machine has two network >>>>interfaces, the cause of the Windows client problem may >>>>be the same as mine. >>>> >>>>Regards, >>>>Allen Moy >>>> >>>> >>> >> >> ================================================================= >> 1879: >> Thomas Edison gets an idea, and his brother Timmy says, >> "Hey, what's that thing over your head? >> ================================================================= >> Ron Croonenberg | Phone: 1 765 658 4761 >> Technology Coordinator | Fax: 1 765 658 4732 >> | >> Department of ComputerScience | e-mail : [EMAIL PROTECTED] >> DePauw University | >> Julian Science & Math Center | >> 602 South College Ave. | >> Greencastle, IN 46135 | >> ================================================================= >> http://www.depauw.edu/acad/computer/RonCroonenberg.asp >> ================================================================= > ================================================================= 1879: Thomas Edison gets an idea, and his brother Timmy says, "Hey, what's that thing over your head? ================================================================= Ron Croonenberg | Phone: 1 765 658 4761 Technology Coordinator | Fax: 1 765 658 4732 | Department of ComputerScience | e-mail : [EMAIL PROTECTED] DePauw University | Julian Science & Math Center | 602 South College Ave. | Greencastle, IN 46135 | ================================================================= http://www.depauw.edu/acad/computer/RonCroonenberg.asp ================================================================= _______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
