JakeG

Don't give up hope. This forum is a wealth of information and there are plenty of folks in here that are ready to help when you get stuck. I'm a C# developer by day, so the programming side comes pretty easy for me. I absolutely love the fact that I can program, test, and debug using .NET. On the other hand, I'm a complete newb when it comes to building circuits, etc. I've learned a ton from this forum which seems to be growing everyday. So hang in there and we'll be there when you need us.

Woo hoo! I was able to get my Netduino to connect using a static IP address!!

I believe the issue had to do with a combination of a bad Ethernet wall jack in my office and (possibly) some mac address strangeness on my router. I decided to change the entire IP address range on my router to see if that could be the issue... yeah, I'm trying just about anything at this point. When I applied the settings my IP reservation for the netduino disappeared, even though other reservations I have on my network remained. I re-entered the mac address and now the device can be ping'd and will serve up a "Hello World" over HTTP.

One thing to note is that...

Debug.Print(socket.LocalEndPoint.ToString());

... still returns "0.0.0.0:80". So, for future readers, I doubt this is a good indication of connectivity.

Re: DHCP -
After my success with static IP, I reattempted using DHCP. The Netduino still isn't able to connect via DHCP.

Thoughts on what to do next?

Continuing in my quest to get this working...

I'm beginning to wonder if it's not a DHCP issue but rather a general Ethernet issue. I've tried setting a static IP address and it get's set (i.e. networkInterface.IPAddress returns "192.168.192.42"), however there's no connectivity. I can't ping the device and when I setup a socket to listen on the IPAddress on the socket instance is "0.0.0.0:80".

Is there some sort of test firmware I can run on the device to ensure that this isn't hardware related?


This is the code I'm using to test connectivity with a static IP:

...
// setup static IP
NetworkInterface.GetAllNetworkInterfaces()[0].EnableStaticIP("192.168.192.42", "255.255.255.0", "192.168.192.1");
Debug.Print(NetworkInterface.GetAllNetworkInterfaces()[0].IPAddress); // returns "192.168.192.42"
...
Socket socket = new Socket(AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.Tcp);
socket.Bind(new IPEndPoint(IPAddress.Any, 80));
Debug.Print(NetworkInterface.GetAllNetworkInterfaces()[0].IPAddress); // returns "192.168.192.42"
Debug.Print(socket.LocalEndPoint.ToString()); //returns "0.0.0.0:80"
Debug.Print(socket.Available.ToString()); //returns "0"

Perhaps a silly suggestion, but I made this mistake once with a notebook and this also resulted in only one led on my router burning.

Great point, Stefan. That may be what was going on when I was plugged into the hub (see "Other points of interest" in my original post). Also, to clarify, the three LEDs I was referring to were on the Netduino itself, just to the left of the Ethernet jack (labeled ACT, 100, FDX) - not on my router. Ever since I took the hub out of the equation, I've been consistently getting three lights on the Netduino. Can anyone confirm that this is an indication the Netduino is connected correctly?

Maybe this is a topic for another day, but I was able to plug my laptop into that same (possibly cross-over) Ethernet cable and the laptop could connect to the network without any problems.

Are you using a cross cable on the Netduino by any chance? Tried different (straight) cables?

Unfortunately (for me), I can confirm that I'm using a straight-through cable plugged directly into the back of the router. I've also used different straight-through cables and different routers.