×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 22/03/2008, at 12:00 AM, Bradley V. Stone wrote:
Not if you're just worried if your TCPIP is setup properly, which I
believe
was the point I made to the OP about using PING to verify DNS is
set up
properly.
Successful name resolution does not indicate that TCP/IP is set up
properly. It just indicates the host on which you are running ping
(in this case) can find the DNS, or possibly host table because there
is no way to control, nor indication, that DNS was actually used.
It is quite possible to have name resolution complete successfully
and still have an incorrect TCP/IP set up that stops packets getting
to other sub-nets or out into the wide world. More awkward are those
cases where the packets arrive at the target destination but cannot
be returned successfully (due to incorrect configuration rather than
being dropped by the target or by a device along the route).
Suggesting to someone that if ping resolves names then TCP/IP is
"setup properly" is misleading at best. If, for example, the host
table was used by ping to resolve names then they could have a
completely cocked up configuration but you would tell them the it's
OK and the problem must be elsewhere.
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
midrange.com
