Tor- Simon Law wrote: <snip about needing to set up dynamic IP addressing on a client>
> As far as Windows services and protocols are concerned, they want me > to start up: Client for Microsoft Networks, IPX/SPX, NetBEUI, and > TCP/IP. I'm using an ISA D-Link DE250CT card, but I think I've > successfully loaded up the module as dmesg | more, shows it detecting > the right IRQ and the I/O address I gave it. > > Thanks for any help you can give me! > > Yours, > Simon It's been my experience that when installing Debian I don't worry about the dynamic IP addressing at that point; instead, I just pick a "safe" IP address and plug it in temporarily during the network setup. Later, after the base install, I go back and add dhcpd (the client is dhcpd; the server is dhcp (I believe)). This dhcpd client will allow your client PC to pick up dynamic IPs from your campus network, including such things as subnet masks and gateways, etc. I've never had to deal with IPX/SPX, so I don't know what's involved there, but I do believe it is a supported protocol on Linux, so maybe someone else has some info on it. As far as NetBEUI goes, I believe you'll find smbfs[x] (x for kernel versions greater than 2.1.70 I believe; non-x for previous kernel versions) to be what you want. I believe you'll need to recompile your kernel so that it has support for Microsoft lanman shares (WFW, Win95, etc); I'm not sure exactly what it's called, but I think you'll recognize it when you see it. If you've never compiled a kernel before, it can be a daunting thought, but it gets easier with experience. After getting that support compiled into your kernel and rebooting, you'll need to install the smbfs[x] package. You don't need the Samba packages; that allows you to turn your Linux box into a Wwindows-style server (for example, if you wanted to share your printer or files to Windows clients). smbfs[x] to be a Windows client; Samba to be a Windows server.
