Re: vb.net and sockets bug?
- From: "Henning Krause [MVP - Exchange]" <newsgroups_remove@xxxxxxxxxxxxxxxxx>
- Date: Mon, 2 Apr 2007 07:50:25 +0200
Hello,
please post your code here.
Best regards,
Henning Krause
"buc" <bucrepus@xxxxxxxxxxxxxxxxxx> wrote in message news:%23$fZOhMdHHA.1000@xxxxxxxxxxxxxxxxxxxxxxx
Yes, I bind to a port, for example 9001, and 9001 is placed into the packet as the destination port, but the source send port is in the 2000 range. This appears to be a bug, and is easily reproducable with only a few lines of code. Even example code from the MSDN. I tried the same code on XP or 2003 server platform with the same results.
BUC
"buc" <bucrepus@xxxxxxxxxxxxxxxxxx> wrote in message news:uBnKlcKdHHA.2068@xxxxxxxxxxxxxxxxxxxxxxxWhy does VB.NET UDP sockets send data on random ports?. If I set a simple socket up to transmit a UDP packet on a port, look at the packet with a sniffer, the actual packets source port and dest.port are diff. The packets destination port is correct, but the packets source port it is actually sent from is random. Why? How can I figure out the actual source port windows is using, not what the vb.net socket is fake reporting?
Thanks BUC
.
- References:
- vb.net and sockets bug?
- From: buc
- Re: vb.net and sockets bug?
- From: buc
- vb.net and sockets bug?
- Prev by Date: Re: ASPX C#.NET Equivilent to ASP VBA Code
- Next by Date: Re: windows Vista Media center, About TV Guide
- Previous by thread: Re: vb.net and sockets bug?
- Next by thread: Re: vb.net and sockets bug?
- Index(es):
Relevant Pages
|