.NET and Network Interfaces

  • Thread starter Thread starter Dave
  • Start date Start date
D

Dave

Hi everyone,

I've got a program which sends UDP data which works perfectly on my PC but
not on my laptop. The problem experienced is that sometimes on the laptop
packets that I send just dissapear. There is no error, but they do not
appear on any of the networks I have. After some testing it seems that
whenever there is a network interface which is not working (e.g. network
cable unplugged) this issue pops up, and it hangs around for a while until
some magical event (some combination of reboots, changing network settings,
disabling network interfaces, etc) occurs will it start working again.

I'm stumped here, no errors being thrown makes it hard to debug, and the way
it persists for a random time is annoying as well. Any advice people?

Dave
 
Hi all,

I was asked via email if I was using synch or asynch methods, and thought I
should put all info here. I'm using one thread to send data and one to
recieve. Only once the reciever is up and running do I transmit data though,
so it shouldn't make much difference. Moreso as the first packet I try to
send is a broadcast (to 255.255.255.255) and it's not seen on any computer
on the network.

Dave
 
Hi all,

I was asked via email if I was using synch or asynch methods, and
thought I should put all info here. I'm using one thread to send
data and one to recieve. Only once the reciever is up and running
do I transmit data though, so it shouldn't make much difference.
Moreso as the first packet I try to send is a broadcast (to
255.255.255.255) and it's not seen on any computer on the network.
Click to expand...

I don't have the answer to your problem, but it doesn't sound like a .NET
Framework question, never mind a C# question.

UDP doesn't provide guaranteed delivery in the first place, and while you
should expect it to be more reliable than what you're seeing, the problem
almost certainly lies somewhere in the network and how it is interacting
with the Windows network drivers. I doubt there's anything that can be
done from the .NET side to address the issue.

In other words, you will likely have a lot more success posting your
question to a more relevant newsgroup.

Pete
 
Back
Top