i have a workers computer, that if i go through network places i can access the server. if i ping the server via IP address, it pings just fine. however if i ping it by the host name, it pings somewhere else. here is a direct link to the pinging.http://i301.photobucket.com/albums/nn78/Peeps38/nkellysping.jpgi have uninstalled and reinstalled the application that resides on the server in question, and i can also access any of the files that are shared out from the server. the inability to ping the server is what is stopping the application from running properly. i have checked and rechecked any potential firewalls that may be running (norton and windows are the only two i found and both have been disabled)my first thought was to force the recognition of the ip in the host file. the host file looks like this:# Copyright (c) 1993-1999 Microsoft Corp.## This is a sample HOSTS file used by Microsoft TCP/IP for Windows.## This file contains the mappings of IP addresses to host names. Each# entry should be kept on an individual line. The IP address should# be placed in the first column followed by the corresponding host name.# The IP address and the host name should be separated by at least one# space.## Additionally, comments (such as these) may be inserted on individual# lines or following the machine name denoted by a '#' symbol.## For example:## 102.54.94.97 rhino.acme.com # source server# 38.25.63.10 x.acme.com # x client host127.0.0.1 localhost10.1.10.11 Televantage10.1.10.10 eserver the 10.1.10.11 is the problem server and it is not resolving when pinging the name.i am at a total loss as there are two other computers not 6 feet from the problem pc and they work perfectly fine. any thoughts or ideas would be greatly appreciated thanks Jerry 1 person needs an answerI do too

This smells like a DNS Suffix Search List situation. Whenever a TCP/IP non-Fully Qualified Domain Name (non-FQDN) is entered (i.e. a name without a period (.) in it) the DNS will grab suffixes from a list and try them all out first. This list can be viewed by bringing up a command window and entering the command: ipconfig /alland you will see line(s) labeled "DNS Suffix Search List". It would appear like "epeopleamerica.com" is one of the entries in that list.Alternatively, if you go to the network control panel and Right-click on your network connection and select "Properties" then double-click on the "TCP/IP" entry in the middle window (may have to scroll down) then click "Advanced", then click the "DNS" tab there will be two check boxes labeled "Append primary and connection specific DNS suffixes" and "Append these DNS suffixes". To eliminate this, click the "Append these DNS suffixes" box and remove all entries in the box underneath.Yet another approach would be to make your non-FQDN become qualified by ending it with a period. So instead of: ping Televantagetry: ping Televantage.Then it would not append suffixes to the name when resolving the name.You see it in "My Network Places" because it finds it using NetBT broadcasts (Microsoft Networking) which is a different protocol from the straight TCP/IP that "ping" uses. (Different rules are in place for resolving names in these two protocols).HTH, JW