Yes, it seems no matter what I change about the TCP/IP connection properties (in response to the post above, again I point out there is no single character entry in my HOSTS and since then I have found that PING * produces the same result; why it is choosing that specific domain is what I am now...
Sorry, perhaps I emphasized the wrong point. It's not whether the IP is "known" that puzzles me; it's
1. how passing "?" as an argument to PING somehow translated into my entire host.domain; and
2. how whether it was wildcarded or not (e.g. passing a "*") it happened to choose my external...
By the way, I think it's clear upon re-reading what I wrote that what I was *trying* to do was get the syntax for PING, which I would have gotten by "C:\> PING" by itself, "C:\> PING /?" or even "C:\> PING -?" ...
What I ended up doing was "C:\> PING ?" which gave me the IP that XP should...
I have a question pertaining to WinXP's implementation of PING--and probably other MS flavours as well.
I, as I'm sure many other home users do, have a system that hides behind a (insert brand name) consumer home router/firewall. WinXP is set up, again, as I'm sure many other cable modem users...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.