[OpenAFS-devel] Windows Loopback Adapter, revisited

[Lantzer, Ryan]

When my team was working on an unattended install of Windows XP that =
would
join computers to a domain, we needed to address the =
SMBDeviceEnabled=3D0
problem by installing the loopback adapter in an "unattended" fashion.
According to the unattend file documentation for Windows XP, you should =
be
able to install the loopback adapter using the Windows XP unattend file.
Unfortunately, the same unattend file that installed the loopback =
adapter
in Windows 2000 would not install a loopback adapter in Windows XP. When
I requested help from Microsoft, we were told about the applications
devcon.exe and netset.exe. In MS Knowledgebase entry 311272, it =
describes
the devcon.exe application and even gives an example on how to install =
the
"MSLOOP" loopback adapter. It also gives a download link for the
devcon.exe application. The application netset.exe is described in
Microsoft Knowledgebase entry 268781 and is available as a part of the
Windows 2000 Resource Kit tools. I was able to use the netset.exe
application to configure an IP address (a reserved static IP address =
like
192.168.100.1) for the loopback adapter and unbind it from the SMB
server service. Unfortunately, I also had to reconfigure the real
NIC(s) at the same time. I don't know if either of these tools will help
with getting the AFS Client installer to automatically install and
configure the loopback adapter, but they might help someone deploy
the AFS Client at their organization.

I tried to follow the directions you have given for attaching the AFS
Client to ONLY the loopback adapter on Windows XP, but I had trouble
determining the LANA number of the loopback device. By trial and error,
I found it on LANA 3 on the particular computer I was working on. Do you
know an easier way to get a list of LANA numbers in Windows XP? I think
that it would be particularly useful if the automatic LANA detection
were to bind only to the loopback adapter, if it is present. If the
loopback adapter isn't present, then the default behavior of attaching
to all interfaces would probably be appropriate.

If we can bind the SMB server for the AFS Client ONLY to the loopback
adapter, then we might be able to register the name "AFS" only on the
loopback adapter, without having to worry about name conflicts (or maybe
ignoring name conflicts?). When I get a chance, I will try this out to
see if I can get URLs like \\afs\root to work instead of having to use
URLs like \\%COMPUTERNAME%-afs\root. I'm not sure exactly what would
happen if another computer on the network were using the name "AFS", but
it shouldn't be too hard to figure out. If we could get this to work, =
then
we might not need to restrict Windows Computernames to 11 characters or
fewer at our site.

Ryan Lantzer


-----Original Message-----
From: Scott D. Williams sdw@email.unc.edu=20
Sent: Tue, 12 Nov 2002 12:14:34 -0500=20
Subject: [OpenAFS-devel] Windows Loopback Adapter, revisited=20

Hello,
I've done some more testing with the loopback adapter. I now believe I =
was=20
on the wrong track with adding service dependencies to delay the start =
of=20
the afsd service.  Instead, reducing the functionality of the adapter to =

bare the necessities looks more promising. Initial results are positive=20
with several XP and 2000 machines using the following procedure:

1. Install the Windows Loopback Adapter (included w/XP & 2000... NT4?)

2. Configure this adapter ( network control panel, right =
click->properties)
'General' tab:
	'Client for Microsoft Networks' 	off/UNchecked
	'File and Printer Sharing...'	off/UNchecked
	'Internet Protocol (TCP/IP)'	on/checked

Select 'Internet Protocol (TCP/IP)', click on properties
'General' tab:
	choose 'Use the following IP address'
	enter:
		IP Address:  169.254.25.129
		Subnet mask: 255.255.0.0

	click on 'Advanced' button:
		'DNS' tab:
			UNcheck 'Register this connection's address in DNS'
		'WINS' tab
			UNcheck 'Enable LmHosts lookup'
			choose 'Enable NetBIOS over TCP/IP

Save these settings.

3. In the AFS Client control panel dialog
'Advanced' tab
	click on 'Miscellaneous'
	uncheck 'Automatic Lana scan'
	enter Lana number of Loopback adapter.

Restart... should be using loopback now.


Notes:
- The IP address I've given is the one Dhcp has chosen all the machines=20
I've worked on. Also, this is the address I've seen in newsgroups=20
discussing the loopback adapter. Still, no guarantee that it's =
available...
- I have not had to make any alterations to the=20
/system32/drivers/etc/hosts  file.
- No testing has been done on NT4

I have modified my copy of src/winnt/afsd/smb.c to select the loopback=20
adapter under 'Automatic Lana scan'.  I'd like to do a bit more testing =
--=20
and get some feedback - before posting the diff and/or considering=20
installer implications.

--Scott