View single post by freak69
 Posted: Saturday Dec 27th, 2014 04:00 pm
 PM  Quote  Reply  Full Topic 
freak69

 

Joined: Sunday Aug 9th, 2009
Location: United Kingdom
Posts: 28
Status: 
Offline

  back to top

Hi,
Many thanks for your reply.I am certain there are no network issues, since both the ETH03 and remote server (PC) are on the same LAN segment (PC has no FW running). I can ping and connect to the ETH03 from anywhere on the network, no problem, and I can confirm the PC server port I want the module to connect to is open as I get valid data when I telnet to it myself from a second PC. An incorrect setting should be easy to spot as I'd see the failed connection attempt when I run wireshark on the server PC.
My main problem I believe is that I am unable to get the ETH03 into server mode. I try the following:
- Change the IP address.  - works, but a reboot resets back to DHCP.- Change port 1 on server mode to another value, say 10000 - doesn't make any change, still the default on 1001 is accepted and no connection on port 10000.- Change the mode to client mode - ETH03 does not make a connection. Netstat and wireshark on the windows PC confirm this (no data coming from eth03's IP address), as does a telnet, since I can still connect to its port 1001, meaning it is still in server mode, not client mode?- same as above with client/server mode
The first thing I did when I got the module online was to upgrade the firmware from 1.06 to 1.15, wondering if this is an issue. I cant confirm that it was working before as I never tried it. Also, I noticed that with 1.06, the Web (demo) button was active and worked with a small web page. Now on 1.15, it is greyed out. Perhaps it might be worth reflashing the old version 1.06 if you can give me a link to download it?
Lets get this working first and can then work on the other issues later.
ThanksPaul

 Close Window