Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 137941 - Last Review: January 19, 2007 - Revision: 1.2
Callback Security Available Only from Microsoft Windows NT
This article was previously published under Q137941
When you use Dial-Up Networking to dial into a Point-to-Point Protocol
(PPP) or Remote Access (RAS) server, callback security may not work
properly and the connection may fail.
The Windows Dial-Up Networking client supports the callback security
feature only from a Microsoft Windows NT 3.x or 4.0 RAS server. Also, the
default properties of the modem initialization string in the Windows
client disable the modem's auto-answer feature.
The Dial-Up Networking client supports only the CallbackCP control
protocol for processing server callback security services. Currently,
Windows NT 3.x and Windows NT 4.0 support this protocol.
PPP and RAS servers for other platforms and operating systems would have
to use the Microsoft CallbackCP protocol in order for the Dial-Up
Networking client to access their callback security services.
To allow the Windows client to answer the callback verification from a
Windows NT 3.x or 4.0 RAS server, follow these steps:
- In Control Panel, double-click Modems.
- Click the modem you are using, and then click Properties.
- On the Connection tab, click Advanced.
- In the Extra Settings box, type the following line:
AT S0=1
This string allows the modem to answer the callback from the Windows NT
server.
- Click OK or Close until you return to Control Panel.
Callback security can be used to audit the use of remote servers using
either of the following methods:
- The first method is for the remote user to dial into the server and
enter a phone number for callback. After the remote user enters the
callback number, the connection is dropped and Windows waits for the
Windows NT server to call back to establish the remote session.
- The second method is to have a server-side preset phone number. When
the remote user calls in, the Windows NT server checks the user list
for a phone number. At that point, the connection is dropped and the
Windows NT server calls the preset number. The preset number can be
changed only at the server side.
APPLIES TO
- Microsoft Windows 98 Standard Edition
- Microsoft Windows 95
| kbdialup kbnetwork kbprb KB137941 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate