![]() |
Home | Site Map | How To | Windows Vista | Case Studies | Articles | Forums | Services | Donations | Careers | About Us | Contact Us| |
|
Using Netsh command to troubleshoot NAT issuesWith Windows 2003, you can use Netsh Routing IP NAT Commands to troubleshoot NAT issues. For example, Netsh Routing IP NAT show interface displays the following information that may help you to check the NAT settings. NAT LAN Configuration --------------------------- Mode : Private Interface NAT WAN Configuration --------------------------- Mode : Address and Port Translation with Firewall Enabled NAT Static Port Mapping Configuration ------------------------------------- Protocol : TCP Public address : 0.0.0.0 Public port : 21 Private address : 127.0.0.1 Private port : 21 Protocol : UDP Public address : 0.0.0.0 Public port : 500 Private address : x.x.x.x Private port : 500 Protocol : UDP Public address : 0.0.0.0 Public port : 4500 Private address : 127.0.0.1 Private port : 4500 Protocol : TCP Public address : 0.0.0.0 Public port : 3389 Private address : 127.0.0.1 Private port : 3389 Protocol : UDP Public address : 0.0.0.0 Public port : 1701 Private address : 127.0.0.1 Private port : 1701 Protocol : TCP Public address : 0.0.0.0 Public port : 1723 Private address : 127.0.0.1 Private port : 1723 NAT Internal Configuration --------------------------- Mode : Private Interface Related Topics Troubleshooting Windows NAT issues
|
|
|
|
This web is provided "AS IS" with no warranties.
Copyright © 2002-2007
ChicagoTech.net,
All rights reserved. Unauthorized reproduction forbidden.