 |
 |
 |
 |
I have seen the exact same symptoms when using HP FACSNet as a client to
connect to the VAX FACSNet server. In our case, if the message "Connecting
to remote FTP host now..." doesn't change to "Connected now..." in 15 seconds,
I know that it will never connect. I am also using an HP9000/340 with
FACSNet v1.1.2.
Here are some other observations that I made. This problem usually occured
on the first login after the HP was turned on for the day (we usually turn
it off at night, and once it is turned on in the morning, it stays on for
the remainder of the day). Some people would have to reset (reboot) the HP
3 or 4 times before they got a successful login. I usually didn't have a
problem, and really had no idea what was causing (their) problem. :)
Then I realized that when I used FACSNet, I usually started FACSNet from
MasterPage, then walked away for a time (hey, I'm a busy guy!) :) and came
back anywhere from 5 to 30 minutes later to actually login. This lead to our
current protocol, which has cut down drastically on login failures. Quite
simply, we wait at least 1 to 2 minutes after the FACSNet login screen appears
before initiating a login with the F1 key. I imagine that an equally good
solution would be to leave your HP on at all times.
My "theory" is that after turning the power on, the ethernet card isn't
quite initialized completely until after the first time you run FACSNet. (It
probably needs the 'nfg' commands)? Furthermore, the ethernet card needs
some extra time after this initialization before it is completely ready to
communicate.
-----
On another (related) topic, the only .db file that I have found useful to
edit is #11:/WORKSTATIONS/SYSTEM/net.db. There are two items in particular
that have proven useful for my network connection. The first has to do with
subnetting, and subnet masks. As installed, HP FACSNet will continuously
request the current subnet mask from the network, even if your network does
not use subnetting (I'm not sure about the frequency; probably every 1 to 2
minutes). Admittedly, this does not cause a great deal of network traffic,
but you can edit net.db to tell FACSNet what the current subnet mask is (or
the fact that your network does not use subnetting). The other useful thing
to set in net.db is the address of your LAN's router, or gateway. This
would allow you to login from your HP ftp client to a remote ftp server
that is not part of your LAN.
If there is an interest in obtaining procedures to edit the net.db file, I
may post the instructions and/or make provisions for ftp/web access to a
(yet to be typed) instructions document.
/\/\/\_ Eric Van Buren, vanburen%flovax.dnet@rocdec.roc.wayne.edu
\ \ \ Immunology & Microbiology
\_^_/ Wayne State University, Detroit, Michigan
GLIIFCA 4. Sep 29-30, Oct 1. Detroit.
|
|
|
|