<SNIP>
If the "Log onto Network" box is checked, DUN attempts to logon to an NT
DOMAIN.
Thus, if it does not exist (NT Server), it will take 95 a few seconds
longer to go
through the process. I have several small NT networks that I have set
up using IPX/SPX.
If the box is not checked, and you try to logon to a NT server, another
prompt will
appear to logon to the network (NT).
It actually saves a step or two if you are using DUN to get into a NT
server/domain.
I have also noticed that bringing up a terminal window after dailing,
will "fix" alot
of error messages such as "unable to establish network protocol" and
others. Seems
DUN gets in an awful hurry to send login information( as soons as it
detects carrier).
If your good 'ol PM isnt ready, DUN get confused. By bringing up that
window, and having
the customer wait for the Login: prompt, is forces DUN to wait a sec,
and the everything
works perfectly. I have seen this when no matter what I do for a
customer, settings
everywhere verified, the only way he can get through is to bring up
this terminal window.
I have started making this standard practice, even changed my distro
software to do so.
This allows customers to see any messages <PM Login prompt> and saves
ALOT of troubleshooting
on the phone about error messages.
Ron Long
Sage Communications