GHI provides you with the Mac address on a little sticker then it is up to you to program it or program your own. This should be explained in the emx manual
I doubt that the problem you are seeing is related to mac address or DHCP.
I notice that you have System.Net.Dns.GetHostEntry() in the code. Does it always work on every deploy? If the answer is yes. Then you don’t have a problem with the networking stack. and I recommend that you check the server you are connecting to.
If you like try to connect to any http server on the web, this way you make sure that you are connecting with a reliable server.
If it is a wifi connection, make sure that the signal is good.
notice that you have System.Net.Dns.GetHostEntry() in the code. Does it always work on every deploy?
What does this mean?
I cut and paste the same string when this fails on the internet explorer and I see it works. So I think the server is good.
I had once put yahoo.com and that also got stuck. So I think it is not server related
You mean that the server you are trying to access is a public web server? If this is true, and socket.connect() is not working, I don’t want to mislead you. but it could be a hardware or connectivity issue. The cable, the router.
Are you using EMX Development System or it is a custom hardware?
You need to investigate that more Microt, there is something wrong.
So I took it to my customer place thinking it could be just my router set up. And felt bad that it did not work.
Our competitor was able to connect to the customers web server with no issues. They are using some other .NET board inside.
Our set up is a custom EMX board.
There is also a private server running(for set up) on the same EMX at port 22 and that works without any issues. So I think the connections are good. It is only the client that is sending data to the server that hangs most of the time
.NET MF devices share the same TCP/IP stack. it is either RTIP stack by EBSnet which is the reliablly used for years or lwIP which is not used a lot yet with NETMF.
Currently we use RTIP with EMX.
So if the competitor is using a NETMF board, then it is most likely the same TCP/IP stack.
For the problem you are facing, is there a way that you sniff the Ethernet packets? It might give you some clue. Also if you have a code that shows the problem, we can check it for you.