Search /
Docfinder:
Advanced search  |  Help  |  Site map
RESEARCH CENTERS
SITE RESOURCES
Click for Layer 8! No, really, click NOW!
Networking for Small Business
TODAY'S NEWS
• Apple tops the $100B+ tech club
• Microsoft details Windows 8 for ARM devices
• Blogger exposes major Google Wallet security flaw
• Web app lets enterprise set security, sharing for Google Apps users
• Cloudscaling to offer OpenStack private cloud platform
• Valentine's Day Patch Tuesday: Microsoft to issue 9 patches, 4 critical
• Mobile World Congress sneak peek: Quad-core smartphones, Ice Cream Sandwich & more
• Microsoft details 'Windows on ARM' program
• March debut of 'iPad 3' a sure bet, says analyst
• Resume Makeover: How an Information Security Professional Can Target CSO Jobs
•
• FBI unbolts Steve Jobs 1991 investigation file
• Cisco boosted profit, sales in Q2 while cutting costs
• Macs take on the enterprise
• Four crazy tech ideas from Google's Solve for X project
•
/

When pinging falls on deaf ears

By Ron Nutter
Network World Fusion, 11/13/00

I can't ping my router from one of my NT servers. I can ping all other machines on the subnet. For example, if the router is 10.1.1.1 and another machine is 10.1.1.8 and my machine is 10.1.1.40, I can ping the other machine from my machine but can't ping the router from my machine. I can ping the router from any other machine.

Felix Edosomwan

Check the IP configuration of the machine you can't ping the router against one of the other machines on the network. It could be something as simple as a different default gateway or even a missing one. If this doesn't work, try updating the driver for your network card or reapplying the latest NT service pack on this server. If this doesn't help, open up a command window and execute the "Route Print" command. This will give you a text listing of all the IP routes that the server recognizes. Execute this same command on the workstation/server that can successfully ping the router and see if you notice any differences. As a last resort, remove the IP protocol from the worsktation, reboot, reinstall and reconfigure the IP protocol.

If you're still having problems, borrow a protocol analyzer to see why the router isn't responding to the ping request from the NT server. This may seem extreme, but it's the one tool that will give you an idea of what's causing the problem. I had a situation several years ago where a bank network was locking up every few minutes. After running a protocol analyzer on the network for less than five minutes, I noticed a pattern of communications that were abnormal. The tool helped me identify an NLM on one of the Novell servers that was essentially doing a broadcast storm.

RELATED LINKS

Nutter's Help Desk archive

Help Desk forum
Post and answer networking questions.

Ron Nutter, a Master Certified Novell Engineer and Microsoft Certified Systems Engineer in the Lexington, Ky., area, tracks down the answers to your questions. Send your questions to helpdesk@networkref.com.

Microsoft Windows NT Server support

TCP/IP essentials
No network professional should be without these 10 TCP/IP troubleshooting tools and utilities.
Network World, 01/10/00.


NWFusion offers more than 40 FREE technology-specific email newsletters in key network technology areas such as NSM, VPNs, Convergence, Security and more.
Click here to sign up!
New Event - WANs: Optimizing Your Network Now.
Hear from the experts about the innovations that are already starting to shake up the WAN world. Free Network World Technology Tour and Expo in Dallas, San Francisco, Washington DC, and New York.
Attend FREE
Your FREE Network World subscription will also include breaking news and information on wireless, storage, infrastructure, carriers and SPs, enterprise applications, videoconferencing, plus product reviews, technology insiders, management surveys and technology updates - GET IT NOW.