remote network management provided via SNMP in cisco routers(2600,2950,2500 etc)?
475520
Yes they all support snmp. Take a look at the examples. \nhttp://www.netcraftsmen.net/welcher/papers/snmprouter.html
313222
I have no idea.  This is the computer networking area.  Please resubmit your question in the appropriate area.  Thanks.
50448
What exactly is the question? If your tring to download driver information then i've provided a source for a NDISwrapper list, my networking card uses the driver based on the rt2500 chipset, so I hope that helps.
975258
The IANA manages these assignments to allow private enterprises to write their own SNMP MIBs.  Not sure of the exact question, but the private enterprise MIB is identified by 1.3.6.1.4.1 and is the same as iso.org.dod.internet.private.enterprise.  The following number denotes the enterprise itself, for example, cisco is 9, so 1.3.6.1.4.1.9 is iso.org.dod.internet.private.enterprise.cisco for example.
354670
Check out Cisco's CCNA Portable Command Guide for configuration.  www.ciscopress.com or ISBN 1587201585.
51895
First, I'd look for something most providers will consider "small" like a Cisco 1700 or 1800 or AdTran's NetVanta 3000 family.  I'd also insist on integrated CSU/DSU (it makes troubleshooting and racking a lot easier, probably costs less too).  Expect to spend in the vicinity of $2000 on the equipment.\n\nA well configured router can run uninterrupted for years. The trick is getting it properly configured to begin with (the NSA publishes some suggestions, although they're pretty advanced) especially since it'll be exposed to the Internet.\n\nIf you decide to go with Cisco (and I highly recommend them for set-it-and-forget-it reliability) you should contact a local Value Added Reseller to sell you the equipment and install it for you.  If they quote you more than their minimum engagement (4 hours is typical for a minimum block of hours you can buy) they're on crack and you should call another.  Link below is Cisco's reseller locator.\n\nIf you're in California, I can highly recommend FusionStorm, WAMS, and ePlus.  In Ohio you could try eVelocity.
676127
the number of router is the first thing to consider.. for a small network and and simple topology only RIPv1 or v2 can works very well!\nbut if you have a complex topology.. EIGRP is the best one to choose.\n\nalso you need to know which protocols are supported by your routers, you can't run EIGRP on a non cisco router for exemple.\n\nalso the capacity of your routers, OSPF or EIGRP need more pwerful routers then RIP for exemple\n\nhope this can help
736426
read here \n\nhttp://articles.networktechs.com/58-p1.php\n\ngood luck
419803
Please read theres two articles if you are still have problem. Please provide a detail describe of the problem.\n\nhttp://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/networking/rmotevpn.mspx\nhttp://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/networking/vpndeplr.mspx
556487
Assuming that the router is uplinked to your cisco via the ethernet, verify that the ethernet port on either device is being limited in anyway.\n\nAlso, triple-check your cisco config. Are you confident that the T1s are "bonded" properly, and that your ISP is returning traffic to you across both T1's equally? You can check this by doing a "sh int" on each T1 port and noting the incomming/outgoing bandwidth stats.
776975
Hi. Looks more like a LAN connection. : http://www.cisco.com/warp/public/121/paa3oc12_6188.html
328743
on an NT 4 network?  not unless you have some sort of remote desktop software like pcanywhere on it.  then you could bring up the DHCP management console and check the settings.  NT4 dosent use MMC so you couldnt install the DHCP server plugin like you could in a 2k or 2k3 enviroment.\n\nhe said from the client, not the server
550294
Description\nThe /usr/sbin/ping command sends an Internet Control Message Protocol (ICMP) ECHO_REQUEST to obtain an ICMP ECHO_RESPONSE from a host or gateway. The ping command is useful for:\n\nDetermining the status of the network and various foreign hosts. \nTracking and isolating hardware and software problems. \nTesting, measuring, and managing networks.\nIf the host is operational and on the network, it responds to the echo. Each echo request contains an Internet Protocol (IP) and ICMP header, followed by a timeval structure, and enough bytes to fill out the packet. The default is to continuously send echo requests until an Interrupt is received (Ctrl-C).\n\nThe ping command sends one datagram per second and prints one line of output for every response received. The ping command calculates round-trip times and packet loss statistics, and displays a brief summary on completion. The ping command completes when the program times out or on receipt of a SIGINT signal. The Host parameter is either a valid host name or Internet address.\n\nBy default, the ping command will continue to send echo requests to the display until an Interrupt is received (Ctrl-C). The Interrupt key can be changed by using the stty command.\n\nBecause of the load that continuous echo requests can place on the system, repeated requests should be used primarily for problem isolation.\n\nFlags\n\n-c Count Specifies the number of echo requests, as indicated by the Count variable, to be sent (and received). \n-w timeout This option works only with the -c option. It causes ping to wait for a maximum of 'timeout' seconds for a reply (after sending the last packet). \n-d Starts socket-level debugging. \n-D This option causes a hex dump to standard output of ICMP ECHO_REPLY packets. \n-f Specifies flood-ping option. The -f flag "floods" or outputs packets as fast as they come back or one hundred times per second, whichever is more. For every ECHO_REQUEST sent, a . (period) is printed, while for every ECHO_REPLY received, a backspace is printed. This provides a rapid display of how many packets are being dropped. Only the root user may use this option. \n\nNote: This can be very hard on a network and should be used with caution. Flood pinging is only permitted by the root user. The -f flag is incompatible with the -i Wait flag. \n-I a.b.c.d Specifies that the interface specified by a.b.c.d is to be used for outgoing IPv4 multicasts. The -I flag is an uppercase i. \n-o interface Specifies that interface is to be used for outgoing IPv6 multicasts. The interface is specified in the form 'en0', 'tr0' etc. \n-i Wait Waits the number of seconds specified by the Wait variable between the sending of each packet. The default is to wait for one second between each packet. This option is incompatible with the -f flag. \n-L Disables local loopback for multicast pings. \n-l Preload Sends the number of packets specified by the Preload variable as fast as possible before falling into normal mode of behavior (one per second). The -l flag is a lowercase l. \n-n Specifies numeric output only. No attempt is made to look up symbolic names for host addresses. \n-p Pattern Specifies up to 16 'pad' bytes to fill out the packet you send. This is useful for diagnosing data-dependent problems in a network. For example, -p ff fills the packet with all 1's. \n-q Specifies quiet output. Nothing is displayed except the summary lines at startup time and when finished. \n-r Bypasses the routing tables and sends directly to a host on an attached network. If the Host is not on a directly connected network, the ping command generates an error message. This option can be used to ping a local host through an interface that no longer has a route through it. \n-R Specifies record route option. The -R flag includes the RECORD_ROUTE option in the ECHO_REQUEST packet and displays the route buffer on returned packets. \n\nNote: The IP header is only large eno
302373
Is the server an AIX machine? If so, it was probably installed with the OS. 1058 is the standard port for nim, disable/uninstall it if you don't need to install stuff through the network.\n\nIf it's not an AIX box, I have no idea why it's there :-)
799638
Run Nmap from a computer outside of your home network to test all 65535 ports. Doing it one by one is such a hassle.\nhttp://insecure.org/nmap/
939682
1.Don’t think you can which is why we use hardware VPNS but I think I saw some cisco software that would allow multi vpns A better way of doing it is to daisy chain your VPNS together under different ip ranges \n\n2.Not to sure but I would think that limitations to ip rages are standard they are in 2003 server another way of looking at it is to lock down via subnet mask? \n\n3.I usually charge!
553597
Type the following in the command prompt window.\nping 127.0.0.1\n(This runs a loop back test through your NIC.)\n\nThe result must look as follows:-\nPinging 127.0.0.1 with 32 bytes of data:\n\nReply from 127.0.0.1: bytes=32 time<1ms TTL=128\nReply from 127.0.0.1: bytes=32 time<1ms TTL=128\nReply from 127.0.0.1: bytes=32 time<1ms TTL=128\nReply from 127.0.0.1: bytes=32 time<1ms TTL=128\n\nPing statistics for 127.0.0.1:\n    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),\nApproximate round trip times in milli-seconds:\n    Minimum = 0ms, Maximum = 0ms, Average = 0ms\n--------------------------------------------------\nipconfig /all\n\n(This displays configuration details of your NIC)