Cisco Socket Error 161
Contents |
Help Follow Us Facebook Twitter Google + LinkedIn Newsletter Instagram YouTube DirectoryNetwork InfrastructureWAN, Routing and Switching LAN, Switching and Routing Network Management Remote Access Optical Networking cisco tftp socket error Getting Started with LANs IPv6 Integration and Transition EEM Scripting
Tftp Socket Error Cisco Switch
Other Subjects SecurityVPN Security Management Firewalling Intrusion Prevention Systems/IDS AAA, Identity and NAC Physical Security MARS error opening tftp socket error cisco Email Security Web Security Other Subjects Service ProvidersMetro MPLS Voice Over IP XR OS and Platforms Video Other Subjects Collaboration, Voice and VideoIP Telephony Video Over IP Jabber Clients Unified Communications Applications TelePresence Digital Media System Contact Center Conferencing UC Migrations Other Subjects Wireless - MobilitySecurity and Network Management Wireless IP Voice and Video Getting Started with Wireless WLCCA Other Subjects ServicesCisco ServiceGrid Connected Analytics Smart Call Home Smart Net Total Care Operations Exchange Mobile ApplicationsCisco Proximity Cisco Technical Support Online Tools and ResourcesCisco Bug Discussions Technical Documentation Ideas Cisco CLI Analyzer Support Community Help Data CenterApplication Centric Infrastructure Application Networking Intelligent Automation Server Networking Storage Networking Unified Computing Wide Area Application Services (WAAS) Other Subjects Small BusinessNetwork Storage Routers Security Surveillance Switches Voice and Conferencing Wireless Solutions and ArchitecturesBorderless Networks Collaboration Cisco User GroupsSeattle Cisco User Group (SEACUG) Silicon Valley Cisco User Group (SVCUG) Southern California Cisco User Group (SCCUG) Cisco Certifications Cisco.com Idea Center Cisco Cafe Expert CornerTop Contributors Leaderboards Cisco Live! Events Events Community CornerAwards & Recognition Behind the Scenes Feedback Forum Cisco Certifications Cisco Press Café Cisco On Demand Support & Downloads Community Resources Security Alerts Security Alerts News News Video Cisco Support YouTube Cisco YouTube Blogs Technical Documentation Cisco Products Products Services Services Solutions Solutions Global Support Numbers Cisco Support Community Directory Network Infrastructure WAN, Routing and Switching LAN, Switching and Routing Network Management Remote Access Optical
United States Australia United Kingdom Japan Newsletters Forums Resource Library Tech Pro Free Trial Membership Membership My Profile People Subscriptions My stuff Preferences Send a message Log Out TechRepublic Search GO Topics: CXO Cloud Big Data Security Innovation Software Data Centers Networking Startups Tech & Work All Topics Sections: Photos Videos All Writers Newsletters Forums Resource Library Tech Pro Free Trial Editions: US United States Australia United Kingdom Japan Membership Membership My Profile People Subscriptions My stuff Preferences Send a message Log Out TechRepublic https://supportforums.cisco.com/discussion/10572006/ipsnmp-3-socket-cant-open-udp-socketing | Forums | Networks Networks Register Now or Log In to post Welcome back, My Profile Log Out Recent Activity FAQs Guidelines Question 0 Votes Locked Cisco 2600 router error: "unable to open socket on port 161" By bgallaghe · 9 years ago I have done a bit of research regarding a strange message that is popping up on http://www.techrepublic.com/forums/discussions/cisco-2600-router-error-unable-to-open-socket-on-port-161/ my Cisco 2612 router... It seems to be related to the configuration of the aux line but it does not seem to go away even when i unplug the modem completly. It is as follows:*Mar 1 01:11:19.346: %IP_SNMP-3-SOCKET: can't open UDP socket*Mar 1 01:11:19.346: Unable to open socket on port 161It shows up every 20 or so seconds and it makes configuring the router impossible because it covers up the text you type. As follows is my running config (note that for some reason when I request the config, it goes ... well, CRAZY!) :Cisco_2612#show running-configo ip route-cache protocol on IBuilding configuration...IOS (tm) C2600 shutdoCurrent configuration : 1192 bytes0RELEASE SOFanged stat no ip add!sversion 12.2 no ip roservice timestamps debug datetime msecte-cache0, changed state to shutdownoservice timestamps log datetime msec!tinterface BRI0/01986-2003 by cisno service password-encryptionno ip route-cache:00:17.909: %!Nhostname Cisco_2612he TokenRing0/0, ch!logging queue-limit 100 http server 1 00:03:2enable secret 5 $1$YKaL$vpBJfrP7Y4Xc1Eaf9EJYY1er community public ROisco.com/tac *Mar enable password Ciscoable traps tty Line p!tclock timezone CST -6ner motd ^Ctd *ip subnet-zero**18: %IP_*Mano ip routing367: Unable t!o!n!oip audit notify log******
team • Delete all board cookies • All times are UTC - 8 hours Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group Advertisements by Advertisement Management
ease planning, as well. Free PRTG Download >> What is this? This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions! Learn more Top Tags 5721× prtg 1832× snmp 1460× sensor 930× wmi 620× notifications 463× maps View all Tags SNMP and NAT/PAT Votes:0 Your Vote: Up Down I have a number of devices that are all using private IP addresses. I access them via port forwarding through a Cisco 881 router and everything works fine. I put forwards in for port 161 however I am getting an socket error #11044. Tested with the SNMP test tool and if I point the tool to port 6102 (translated port) I get the socket error. If I use X.X.X.X:6102 it reports nothing found. Is it even possible to monittor private IP devices with PRTG? Tom Goldsberry nat pat snmp Created on Jul 8, 2013 6:03:50 PM by Andrew Marshall (0) ●1 Permalink 5 Replies Votes:0 Your Vote: Up Down So on the Cisco device you are forwarding port 6102 on the public IP address to port 161 on the internal IP address of the device? What kind of device are you trying to monitor behind the firewall? Are you able to read any SNMP values on the device from a computer behind that firewall to make sure SNMP is working correctly? Add comment Created on Jul 9, 2013 9:54:17 AM by Greg Campion [Paessler Support] Permalink Votes:0 Your Vote: Up Down Sorry for the delay. Yes that is correct, 70.102.X.X:6102 port forwards to 10.0.X.X port 161 udp. If I set the sensor up with an ip address of 70.102.X.X:6102 I get the socket error. The devices I am trying to monitor are cisco switches (3548's mostly), SMC switches, motorola access points and Powerdsine POE switches. Originally had a vpn tunnel set-up and was monit