Spinneret...Help!

greenglue

Hi!
I am having difficulty setting up my Spinneret wit the tutorial from here: http://spinneret.servebeer.com:5000/gstart/setup.htm
My router can't seem to detect it even though I put all of the info in correctly, can you assist me please.
Michael

Mike G

Welcome to the forum.

There is not enough information in your post.

What is your Subnet mask (router)?
What is your Gateway (router)?
What is your Spinneret IP and port (code)?
How are you trying to access the Spinneret? What are you entering in the address bar?
Do you have an SD card?

greenglue

Thanks!
Subnet mask: 255.255.255.0
Gateway: 192.168.2.1
Spinneret IP and Port: Not being found by modem, but IP should be 192.168.2.13:5000
I am entering 192.168.2.13:5000 in the address bar in Google Chrome AND in IE. None work, as I said, the Spinneret is not being detected by modem...
Yes I have an SD card, and it is found by the Spinneret and mounted

Mike G

You need to explain your setup.

What do you mean the Spinneret is not detected by your modem? You probably have an Ethernet cable plugged into the Spinneret. Is the other end connected to your router? Is it connected to a switch?
What program is loaded in the Spinneret? Did you see the web server start up in the Serial Terminal?
Can you PING the IP? -> From a command window enter "ping 192.168.2.1".

Please do not alert me through a PM that you have responded. I'll get to your query eventually.

greenglue

The Spinneret is connect directly to the modem via Ethernet cable, the modem has a 'Device Table' and it shows which devices are connected to it, but the Spinneret doesn't show up, not even under the name UNKNOWN. The program is from this link: http://spinneret.servebeer.com:5000/gstart/setup.htm and is fully configured to my network settings. In the Serial Terminal, I see that it detects the SD card, mounts it, then it has a bunch of weird code:

Mount SD Card - OK
Start RTC: 01/09/2000 02:16:43
W5100 Driver Started

Status Memory Lock ID : 1
HTTP Server Lock ID : 2

TCP Socket Listener ID : 0
TCP Socket Listener ID : 1
TCP Socket Listener ID : 2
TCP Socket Listener ID : 3

Started Socket Monitoring Service

Initial Socket States

3-14 2-14 1-14 0-14
clsd open lstn estb clwt clng udps
0000-0000-1111-0000-0000-0000-0000

Initial Socket Queue
FIFO[0] 00000000
//////////////////////////////////////////////////////////////

When pinging it in cmd, this is what I get:

C:\Users\Administrator>ping 192.168.2.23

Pinging 192.168.2.23 with 32 bytes of data:
Reply from 192.168.2.20: Destination host unreachable.
Reply from 192.168.2.20: Destination host unreachable.
Reply from 192.168.2.20: Destination host unreachable.
Reply from 192.168.2.20: Destination host unreachable.

Ping statistics for 192.168.2.23:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Thanks!
Michael

Mike G

Ping looks odd to me. Usually when I ping an IP on my internal network I'm not routed to another IP. Secondly, you said the Spinneret IP was 192.168.2.13. Why are you pinging 192.168.2.23 and 192.168.2.20?

What is the make of your modem? You might have to contact the manufacturer or read the manual.

TechNet wrote:

TechNet
Destination Host Unreachable

This message indicates one of two problems: either the local system has no route to the desired destination, or a remote router reports that it has no route to the destination. The two problems can be distinguished by the form of the message. If the message is simply "Destination Host Unreachable," then there is no route from the local system, and the packets to be sent were never put on the wire. Use the Route utility to check the local routing table.

If the message is "Reply From < IP address >: Destination Host Unreachable," then the routing problem occurred at a remote router, whose address is indicated by the "< IP address >" field. Use the appropriate utility or facility to check the IP routing table of the router assigned the IP address of < IP address >.

If you pinged using an IP address, retry it with a host name to ensure that the IP address you tried is correct.

Again stop PMing me!

greenglue

Sorry about the PM thing, in your earlier reply on this thread I thought you said to PM you.
I messed up on the ping thing, here is the ping for 192.168.2.13.
The modem is a CellPipe modem with Bell in Canada.

C:\Users\Administrator>ping 192.168.2.13

Pinging 192.168.2.13 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.2.13:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Mike G

I don't know anything about the CellPipe modem. Can you ping your host PC, ping another PC on your network, and ping your gateway?

greenglue

Ping with another PC on local network: SUCCESS
Would my gateway be 255.255.255.0 as found in ipconfig or the 'WAN Gateway in the modem'?
Would the host PC be my localhost?

Mike G

WAN gateway but if you can ping another IP 192.168.2.x then I imagine the modem is also a router. Assuming the Spinneret is configured correctly, you'll need to consult your modem documentation for configuration. You might have to assign an IP as the Spinneret is not using DHCP.

greenglue

YAY! I found the problem, I put a 1 instead of a 2 for the IP, I should check the code over more often...
Thanks for your help!
Michael