NONMEM FTP Repository

NMUSERS: Several individuals have observed that the PKPD Repository was unavailable last Wednesday and Thursday. It is now up and running again. Because of the demand, I switched the system over to the Windows NT file system. This will improved access time, provide more flexible security, and offer greater reliability. Also, the system now gives UNIX style listings rather than MS-DOS style listings. This will make it work better with Web browsers and similar programs. Even locally, I find that I often have to access the service "pkpd.icon.palo-alto.med.va.gov" more than once to connect. This seems to be a local internet problem, and not related to the PKPD server per se. I'm working with our local internet provider to fix this. However, as a reminder, if you have difficulty getting access using the name, the IP address itself appears to be 100% reliable. The IP address is 198.31.34.225

I am lost in my efforts to "FTP to pkpd.icon.palo-alto.med.va.gov....or to 198.31.34.225" No matter what I try, what INTERNET Provider I use, I always get "unknown host". Are you out there? Has anyone experience with access from outside the Bay Area?

yesterday (01/24/94) I had tried again unsuccessfully to reach the NONMEM Repository, and I posted a message on the NONMEM User Net. Today (01/25/94) I could reach pkpd.icon.palo-alto.med.va.gov for the first time with FTP through my CompuServe account. The lesson: persistence works on the "information super highway" Thanks to Steve Shafer!

Thanks for the notes. I'm been quite frustrated by the difficulty of accessing the repository via "pkpd.icon.palo-alto.med.va.gov." Even from my own desktop computer, which is separated from the repository by about 5 feet of ethernet cable, I frequently get the "Unknown host" message! However, I've been able to log in via 198.31.34.225 from around the United States, and have heard from others around the world who have been successful as well, both with the IP number and the machine address. I'm starting to suspect that the problem is the name itself, both its length (only 1 character less than the absolute limit on FTP servers) and possibly the presence of the dash in palo-alto". Needless to say, my local IRMS people, when I can reach them at all, are clueless on this one. I'm trying to get an answer from our service provider, Barrnet. However, if I can't resolve it here, I'll just pick up the entire repository and move it to a computer at Stanford. Stanford has installed a new system to provide internet host services (FTP, WWW, etc) to students and faculty for exactly this sort of thing, so that should solve the access problems. I complement you on your persistence. I hope it was worth the effort.