0
C:\>ping localhost

Pinging Vextor [127.0.0.1] with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Control-C
^C
C:\>f:
F:\>ping localhost
Ping request could not find host localhost. Please check the name and try again.
cesara
  • 103
  • 2

3 Answers3

2

For all your windows networking woes, try

netsh winsock reset

and reboot

Visualize
  • 136
  • 2
0

There's a first for everything :-)

Are you sure you are running the same ping (check your path environment variables also) and can you list the contents of F:\? I.e. is the F: partition online/accessible?

DutchUncle
  • 1,265
  • 8
  • 16
  • how do you check if the f: partition is online accessible ? I did check the location of ping.exe -- it is running the same ping... and it is running from c:\windows\system32 ... i even tried to run c:\windows\system32\ping.exe from the f:\ – cesara Mar 01 '11 at 21:13
  • So you can get a dir from F:\ and copy & run files on it? – DutchUncle Mar 01 '11 at 22:27
0

Never seen anything like this, and I'm totally unable to reproduce it anywhere.

The only plausible reason I can see would be if you have an executable file called ping (ping.exe, ping.bat, ping.vbs...) on your F: drive, and that gets called instead of the standard system ping utility. Other than that, I have no clue at all...

Massimo
  • 70,200
  • 57
  • 200
  • 323
  • yes it is very strange. my other machines work fine ... just this particular server doesnt like dns on different drive letters. I've tried rebooting disconnecting drives and still do not work – cesara Mar 01 '11 at 21:15