11 replies to this topic

[spaceyguy]

I've tried about a 5 different ways of doing this, namely this one, and it keeps failing; a System.Net.Sockets.SocketException is being thrown, without much information about what exactly the error is.

[Chris Walker]

Hi spaceyguy, Due to its extremely compact nature, .NET Micro Framework does not have detailed error messages in its sockets library (although it does give a limited number of error codes that may be useful here). Have you set the IP address of your Netduino Plus? Can you ping your Netduino Plus from the other computer? Welcome to the Netduino community, Chris

[spaceyguy]

Thank you for the welcoming. I couldn't ping it at first, finally after struggling with MFConfig I set the netduino up with DHCP and found the IP through my router. Once I got that working I could ping it, but the problem persists.

[Chris Walker]

Hi spaceyguy, Do you have a short example (including the server you're trying to connect to) that you could zip up and attach to your post? Also, have you looked at the SocketClient example which comes with the .NET Micro Framework SDK? If you remove the Microsoft proxy server from it, you should be able to connect to servers on the Internet. Also, please be aware that some DHCP servers are having trouble with the lwIP networking stack used by .NET Micro Framework on the Netduino Plus. We're working on a bug fix to enable wider compatibility with DHCP servers--but you may want to try a static IP address for diagnostic purposes. Chris

[spaceyguy]

When I reconfigure it to use a static IP I can't ping it anymore, even after changing it to several different one (after checking if they weren't taken of course). Even giving it the IP that it had been assigned using DHCP while it hadn't been released it still didn't work.

[Chris Walker]

When I reconfigure it to use a static IP I can't ping it anymore, even after changing it to several different one (after checking if they weren't taken of course). Even giving it the IP that it had been assigned using DHCP while it hadn't been released it still didn't work.

If you configure as static IP and can't ping it anymore, then that's a more general network-related issue (i.e. the router doesn't support static IP clients or there's an address conflict or the gateway/subnet mask are wrong, etc.)

Go back to where you can ping your device, and try running Microsoft's SocketClient sample. That should download a page from the Microsoft website.

Chris

[Frank]

If you configure as static IP and can't ping it anymore, then that's a more general network-related issue (i.e. the router doesn't support static IP clients or there's an address conflict or the gateway/subnet mask are wrong, etc.)

Go back to where you can ping your device, and try running Microsoft's SocketClient sample. That should download a page from the Microsoft website.

Chris

I wholeheartedly agree. I just spent too much time chasing my tail, and it was nothing with the NEtduino or the programming, just a router issue ! And my key was when I couldn't ping the board!

[spaceyguy]

If it is the router, how do I proceed? EDIT: Initial test without the router failed as well.

[Frank]

If it is the router, how do I proceed?
EDIT: Initial test without the router failed as well.

My router problem was based on sheer ignorance, followed by uninformed tweaking! I solved a multitude of home problems when I did a lot of reading, and eliminated my tweaking. If you failed without the router, one of the many real experts will surely help you. This board has good depth in experience.

[spaceyguy]

After enough messing around I got it to work using the SocketServer example at least, I'm not even sure exactly what I did though.

[Chris Walker]

After enough messing around I got it to work using the SocketServer example at least, I'm not even sure exactly what I did though.

Very good news. That means your hardware appears to be working properly. Now to get your socket client project running...

Chris

[spaceyguy]

That is working as well now, I downloaded the sample again after I had changed it. It worked after that, so maybe my changes were part of the problem but I doubt that was all of it. After thinking using the router config more often then normal I noticed problems frequently, so I'm guessing thats the problem.