 |
 |
At 05:12 PM 6/4/2004, Doug Nelson wrote: >John Gorentz writes: > >> I did it the way Chris Harper suggested (using \\cc-pubafs-4.cl.msu.edu) and it worked! So I imagine the numeric address would work, too. It sounds plausible that it's a WINS problem. >> >> I wonder how stable the name cc-pubafs-4.cl.msu.edu is going to be. But I'm going to go ahead and tell our faculty people to use it for now. They're trying to get ready for some classes that will begin week after next. >> >> I'll keep Bill Wheeler's suggestions in mind when we set up our own VPN concentrator. I've ordered a low-end Cisco box for this purpose, rather than use a Win2000 server for it. (No guarantees that I know what I'm doing.) > >John, > >Before you publicize a connection to cc-pubafs-4.cl.msu.edu, try connecting >to \\afs.msu.edu and see if that works. That will avoid troubles if we do >take a computer system out of the rotary for maintenance. > >I will also pass this on to our VPN guy, to see if we can determine what might >be affecting connections via \\afs alone. Our WINS person checked, and WINS >is responding properly here on campus. Doug, I tried \\afs.msu.edu and it does not work. I tried \\cc-pubafs-4.cl.msu.edu again, and I can still make connections that way. I haven't widely publicized the \\cc-pubafs-4.cl.msu.edu , but have made it known to the people trying to get ready for their classes. I also pointed out that it might not be a good long-term solution. John