The Connect() test is trying to reach another host but just for testing purposes.
What I would like to know is whether anybody did ever succeed in doing an Http client request using W5100 chip and new “stack” released with latest SDK.
Since socket.Connect() timeout isn’t settable, could it be too short for some networks?
If you start with a very simple test setup, you will be able to answer the question yourself. If that doesn’t work, then others can help by repeating and analyzing the simple setup.
[quote]So you have a gateway at .252, a DNS server at .120 and a HTTP server at .142
Seems like a complex network situation to start with Smiley[/quote]
I meant the complex setup. Put everything on one network to see if it works at all. Then move to more complex configurations. It’s easier to find problems when there are not so many variables.
another test - once you’ve initialised the Wiz chip, can you PING it’s IP address? And is that MAC address one you made up ? Find your PC’s MAC and change the last two octets and use that, see if it helps (oh gee how I wish Wiz would have provided a valid/registered MAC range that we could use)
Despite I could ping the device, HttpClient calls started to work only when I changed MAC address to replicate the one of my PC with last 2 byte changed.
there was a similar post a week or two ago :). It seems like some switches don’t handle totally made up MAC addresses or certain address ranges. The switch probably discards the traffic as invalid, so that it never gets to the fez.
Most switches and routers will have a problem if the first octet of the mac address is “ODD” or has the least significant bit set to “1”. This is used to indicate a MAC Multi cast. see MAC address - Wikipedia .
Here is the tool I use to create “Safe” mac addresses. http://www.macvendorlookup.com/ as long as you are on you own lan segment you can use any of the addresses it generates, just DON’T use the same MAC on other devices on the same LAN segment. ;D