Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

W2K DUN

Status
Not open for further replies.

DavidDCSA

Technical User
Nov 7, 2001
80
US
I want to establish a DUN session (TCP/IP) to my network, authenticate via my Shiva LanRover and Ace authentication (3rd party security) software. This part works. I then want to start a remote control program (Reachout) to log into our Novell network via a Reachout Host. (I am able to do this in W95 by disabling the "log in to network" option in W95 DUN). Here's the rub, once the authentication (LanRover and Ace) complete, W2K DUN throws up a Log in dialog requesting username, password and domain; when this happens (I do not want it to), my DUN session drops (the LanRover logs it as a normal user disconnect). I have tried removing all protocols from the W2K PC (from which I am dialing) except for TCP/IP, but still W2K wants to authenticate. How do I prevent this?

 
W2K should have the same setting as your win95 but in a different location.

go to the properties of that connection and click on options tab and uncheck "include windows logon domain". i hope that helps but let me know if it don't!! "Jack of all trades. Master of none."
[americanflag]
 
Thanks, interNETech, I appreciate the response.
The information was helpful, it allowed me to determine that the "real" problem was inability of the host and remote to agree on PPP control protocols. Deleting and re-adding the TCP/IP protocol finally resolved the problem.
Thanks again!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top