First, make sure you have the following:
The card should automatically be ready to work on the network as soon
as you insert it or boot in the future. It seems to survive fine
through standby and hibernation modes. You will need to authenticate
through Spinach whenever more
than 24-hours has elapsed since your last authentication.
When you first plug in the WaveLAN card, that router is set to not
forward packets from your machine to the rest of the Stanford network and
world. This is so people from outside can't get a host on our networks
by just bringing a wireless notebook into the building. After you
authenticate, the router is changed to allow packets from your laptop to
go through for a certain time period (24 hours), after which you have to
re-authenticate. The binding of IP address to your WaveLAN card and
the permission to access the internal net persist even if you reboot or
remove the WaveLAN card for a while.
There are a couple ways to do this. Probably the easiest is when you autenticate with Spinach. After authenticating with your leland ID, you will eventually get to a page that says you have access and the IP address which you are using.
Using this IP from the other machine you should be able to map drives that are on your laptop. For example, if you got 171.64.70.158 and you have set your laptop to share the C drive as C$, you could map '\\171.64.70.158\C$'.
Another way to get the IP address is to go the start menu, choose run, then type 'winipcfg' in the dialog box. From the pull down menu choose Wavelan. The dialog should then show in the IP box your temporary IP address, which can be used as above.
Note that you also have a character string machine name which is
something like 'csroam8'. This is displayed at the same place as
the IP during the Spinach authentication, or can be found by typing 'nslookup
171.64.XX.XXX' (where XX.XXX are the appropriate values from your temporary
IP) from any shell prompt on one of the Irix machines. Unfortunately
Windows doesn't seem to accept this name when mapping drives due to some
quirk of Windows networking. This name can, however, be used for
standard TCP based