tags:

views:

357

answers:

4

I have a socket app that passes data between 2 processes. It works fine on a number of computers with the 2 processes running on the same computer. A person in my office visited a government office where they made some unknown changes to her laptop so she could get on their network. When she left the app no longer works.

If she tries to telnet to the listener app she can connect if she tries to connect to the computer name or 127.0.0.1, but connecting to localhost doesn't work. Any ideas?

+2  A: 

Check the hosts file?

Wait; do you mean when she telnets to localhost it works, or when she telnets to her IP it works?

overslacked
Telnet to 127.0.0.1 is fine, but localhost fails. I'll check on the hosts file.
Jake Pearson
I don't mind downvotes, but please leave a comment when you do.
overslacked
+14  A: 

Check the Hosts file, located here: C:\WINDOWS\system32\drivers\etc

This file is what translates localhost to 127.0.0.1

AaronS
+5  A: 

Perhaps the localhost mapping in %systemroot%\system32\drivers\etc\hosts is pointing to an IPv6 address and the program does not support IPv6.

Does the entry in the hosts file look like this:

127.0.0.1 localhost

or like this?

::1 localhost

Please go to start, run, and type:

notepad %systemroot%\system32\drivers\etc\hosts

to check.

Brian R. Bondy
This was exactly the issue. My app was skipping over IP6 addresses. We changed the host and it was fixed. Now I have need to change my app.
Jake Pearson
A: 

Just in case this happens to be a *nix system, you can find the host file here:

/etc/hosts

Andrew Hare