localhost socket connection

[PRSGuitarPlayer]

Greetings:

I have an application that performs a socket connection to a local server
with an address of "localhost," 127.0.0.1 and a port of 3490. The local
server returns a web page using the default browser established in the Vista
OS.

However, when the socket connection is performed, a message appears with a
request to connect to the internet or remain offline. If "offline" is
selected, the web page appears to be taken from cache and not updated. If
"connect" is selected, the web page is updated but then a request is received
to connect to the Inrernet using a DSL connection that is configured in the
system. Although the web page returned from the local server is then updated
with new data, it is necessary to cancel the DSL connection request. This
behavior occurs with each socket connection to the localhost server.

Windows XP does not exhibit this behavior. Rather, Xp makes the connection
to the local server without any messages concerning requests to connect to
the internet.

I looked at Windows Explorer to see if I could find any relavent
configuration problems, but I found none.

How do I stop this unwanted Internet connection behavior when performing
socket connections to a localhost server?

Any suggestions are greatly appreciated.

Thanks
Roy W.

 

[AJR]

Confused here - if the application is on a computer other than the "local
server" connecting to "Localhost" would mean it is connecting to the
computer on which it is installed.

Local host, or it's address 128.0.0.1, provides a means of "pinging" a
computer from it's own keyboard - primarily as a means of checking it's
TCP/IP configuration.

 

[PRSGuitarPlayer]

Hello AJR:

Actually, AJR, the localhost IP 127.0.0.1 is a "private" IP used for
interprocess communications. It is just a special IP that is used for
communications between 2 or more executables on the same computer systrem.

Ping, on the other hand, is a UDP not TCP protocol tool to test the
operability of a connection between 2 IP end points. The IP end points can
be either private or public IP's

My application, which resides on a single computer system, consists of 2
executables in the client/server model. The client sends a request to the
server for a web page. The client connects to the server using a standard
TCP socket connection using 127.0.0.1 (localhost in the System Hosts file)
with a port of 3780. The server "listens" for the connection request,
establishes the connection, and sends back to the client the web page that
was requested.

The application does not function to access the external Internet. Yet, the
Vista OS displays a subwindow which requests a connection to the Internet.
The internal configuration of the computer does include a DSL Internet
configuration but the DSL link is not connected as the application does not
requiire it. Vista, however, seems to be forcing the request on a localhost
connection.

Now on windoes XP, this connection behavior does not occur. I am not sure
if this a OS bug, a valid Vista functional change, or some configuration
problem.