Re: Socket error 10065 with Windows 2000 SP4
From: Stanley Feng \(MSFT\) (sfeng_at_microsoft_dot_com)
Date: 03/02/04
- Next message: Stanley Feng \(MSFT\): "Re: WSAError returns 2"
- Previous message: Eugene Gershnik: "Re: Overlapped IO (Sockets) and _beginethreadEx"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 1 Mar 2004 16:46:15 -0800
Do you mean the backup (connecting peer) cannot reach the master (accepting
peer) even if they are on the same machine? Are we talking about loopback
interface? This sounds quite odd to me...
Just to isolate problems, can you try to write a simple winsock program that
does following simple things: 1)listens on 127.0.0.1, port X, and 2)
connects to 127.0.0.1, port X.?
-- This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples (if any) are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm" "Joanna" <j_heim@yahoo.com> wrote in message news:D430C7D4-CD3D-46F3-B9EE-9F4F5B1111F6@microsoft.com... > We're required to upgrade to Windows SP4 so we loaded SP4 on our development machines to make sure it wouldn't break the application. After loading SP4, we got Socket error 10065 (No route to host). > > The application is setting up a Master Session Manager and Backup Session Manager. The Backup establishes an independent socket connection with the Master. This is for redundancy. However, the Backup can't connect to the socket for transmitting to the Master. (In this case, they are on the same machine. That is, the machine goes out to the network to send itself a message.) The program reads the registry to determine the machine IP and Port which are specified as 127.0.0.1 and 22111, respectively. > > If you know of a fix for this, it would be very much appreciated! Thanks!
- Next message: Stanley Feng \(MSFT\): "Re: WSAError returns 2"
- Previous message: Eugene Gershnik: "Re: Overlapped IO (Sockets) and _beginethreadEx"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
