>>Has anyone gotten this to work? I've tried it on 2 systems using the
>>"Selective Install for Networking" or just running MPTS and Peer Installation.
>>It will not work. The usual symptom is that the Requester service will
>fail to start.
>>The error is something like "The service is not responding to the control
>>"The Requester did not respond to a control signal".
>>I've tried several combinations of NetBIOS and NetBIOS over TCP/IP.
>>latter is used; the requester will not start. NetBIOS by itself is
>fine. If you got it to
>>work I would greatly appreciate some assistance!!!
Hmm.. It took some work, but we got it working here...
BTW, we have a small BootP server that kinda 'Kicks' it into gear...
The main thing, after install of connect & mpts and peer, go under the
mpts and select NetBIOS over TCP/IP on your adapter. Then go under the
EDIT option and set the "NODE" option as H-Node. Also, Set the
"NetBios Name Server Address" and the NetBios Datagram distributer address"
to the NetBios Server (ours is Win-NT 3.51)
After that, close down and exit MPTS...
NOW, this is where it gets tricky... You have to either have :
A) TCP/IP configured by a BOOTP very early in the bootup
we put our bootp in the setup.cmd file in the /mptn/bin/ directory.
this ensures that before anything network happens, IP's are configured.
B) (I assume this would work... never tried it, wouldn't know why people
would even want to...) Manually plug all the IP info in... Server,
Machine IP address... DNS servers... etc...etc..etc...
Doing it all and using A it works... Using B...? I don't know... Like I
said, we use the BootP, it makes for an easy set up of a machine, just
a few lines edited and "plop" the machine is on the network.
have fun, let me know if it helps...
Penn State Fayette Campus Computer Center