Re: WSAAsyncSelect stopped working

That's sounds strange , if it not hard for you to re-install VS2005
afterward , just return to previous state with system restore
( that will be exactly the same ) and try your app there
Arkady

"anonymous" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A2C81B23-2D28-4F28-B777-2EB9AAFC5DC7@xxxxxxxxxxxxxxxx
Just the install. I'm still using the same .exe compiled under VC 6.0.

"Arkady Frenkel" wrote:

Do you mean that just installing VS cause the error or you re-build your
app
in it ?
Arkady

"anonymous" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5D04A4ED-5749-4C25-8183-2EB7A0EB3DA3@xxxxxxxxxxxxxxxx
I'm looking for debugging help.

I have a TFTP-like utility used to download images to devices. Has been
working great. It was programmed in Visual C++ 6.0.

I was trying to see if VS 2005 express would do something I wanted, so
I
installed that on the same machine and around that time, this utility
stopped
working. I'm not sure the two things are related, but maybe.

Basically, the utility sends out a UDP back and waits for an ACK using
WSAAsyncSelect to generate a message. I can see that packet coming into
the
PC correctly using Ethereal, so I know its getting delivered on the
wire.
I
don't have a firewall installed or something along the lines of
BlackICE
that
is blocking any ports.

It just seems like the event generation or winsock UDP receiving has
been
broken. I also have a utility (pumpkin TFTP client) which is broken too
which
appears to use the winsock library.

WSAAsyncSelect returns without error, so I would assume I'd get an even
on
the receipt of a packet, but I don't. I tried just polling with a
select
command and also never receive a packet.

Other TCP based operations seem to work fine on this machine. I'm not
sure
I
have anything else that I normally do which is UDP related to know if
it
is
just this port or something more limited.

Any suggestions on how I can trace where the problem is occurring ?

Netstat -s -e shows the Datagrams sent increase with each send and the
Datagrams Received increase when the packets come in. No Ports and
Receive
Errors do not increase.

Netstat -a shows the UDP port on the PC side open.

I also checked for the message being generated to the window with SPY
and
didn't see it, so its not as if MFC just didn't run the handler for the
message.






.

Relevant Pages

  • Re: WSAAsyncSelect stopped working
    ... Do you mean that just installing VS cause the error or you re-build your app ... It just seems like the event generation or winsock UDP receiving has been ... the receipt of a packet, ... No Ports and Receive ...
    (microsoft.public.win32.programmer.networks)
  • Re: Ports for testing UDP
    ... >> I think that your question is confused and, therefore, confusing. ... The question that you asked (as I recall "how do I know what ports are ... so looking at netstat will tell me all the ports that it's ever going to ... You are assuming I don't know enough about UDP to know how ...
    (comp.protocols.misc)
  • Re: TCP/IP filter & SMTP
    ... > Open up all the ports so that it works. ... > NetMon can be installed from the Add/Remove programs control panel ... >> some sort of UDP packet when I send mail. ...
    (microsoft.public.inetserver.iis.security)
  • Re: iptables: DROP or REJECT?
    ... >wait, then send another syn packet, and possibly repeat several times. ... The remote host ... The other minor advantage of dropping incoming UDP to ... do exactly the same for all ports, and all 139 protocols that are defined ...
    (comp.os.linux.security)
  • Re: UDP & TCP
    ... To display all open ports (TCP and UDP) open cmd prompt and run command: ... To find out which ports are blocked, consult your firewall software. ... If, however, you are not using firewall, then any packet that is received is ...
    (microsoft.public.win2000.security)