لطفا منتظر باشید ...
Publisher| Routing and Remote AccessNotes |
WS2003, W2K, XP, NT, Windows 95/98, Windows for Workgroups, MS-DOS,
and Apple Macintosh.If dial-in or VPN clients can't connect to your
remote access server, there are a number of things you can check:
- Check the modem, modem bank, or other hardware at both the client and
the server. - Make sure the Routing and Remote Access Service is started on the
server by:
select Server Status check server in details pane- To start a stopped server:
select Server Status right-click on server in details pane All Tasks Start- Make sure the remote access server is enabled for remote access by:
right-click on server Properties General Enable thiscomputer as a remote access server
- Make sure your dial-in or VPN (PPTP/L2TP) ports are enabled for
inbound connections by:
expand server container right-click on Ports select device Configure
select Remote access connections- If all your remote access ports are active, you can add additional
ports (easy for VPN ports). - Make sure you have allowed remote access for the
client's user account and, if there is a remote
access policy configured, that the policy doesn't
deny the user access. - Lots of things can go wrong with remote access. Make sure:
- Your client supports the correct network protocol
- You have assigned the client addresses from a correct pool
- You have allowed sufficiently lax authentication and encryption
methods on the server - That a connection can be successfully negotiated with the client
- That the client is using appropriate credentials
- That the client supports the correct tunneling protocol for VPN
connections - That the phone number on the client is configured correctly for a
dial-up connection
See Also
Connections , netsh,
route, TCP/IP
