Network cable length from classic to 4 port switch

[offgridQLD]

I run two classic 150s. They both conect to a 4 port switch and then onto my router (all hard wired) I have a static Ip  for my homes connection and run a static on both classic . I have had  rock solid (remote) connection to both classic via the local app. One classic is on port 502 and the other port 503 and then just use my homes static Ip address for remote connections via the local app. Even when I am at the house and on my local network I just connect to them the same way and its worked great.

This past week the classic on port 503 has been playing up. Often showing up as "device not available" while at the same time the classic on port 502 is rock solid and always a green light.

Sometimes the classic on port 503 will come online for a short time but then drop off again.

So I got to thinking it must be the cat5 cable from the classic on port 503  going to the 4 port switch. I swapped the cable out for a new one and all good for 10 min then again lost the connection with just that classic on port 503 classic on port 502 was fine . So not that cat 5 cable.

Then I took a good look at the two classic to see whats the difference (why is the classic on port 502 so stable and the one on port 503 not)They are both going into the same 4 port switch so it cant be that and they both go to the same router so not that. well all I could pick was the classic on port 503 has a cat5 cable going into the 4 port switch that is about 1/2 the length of of the cable to classic on port 502.

The cat 5 cable is only 2 or 3 feet long on the one dropping out . Perhaps some kind of random feedback going into the 4 port switch because the cable is so short) the classic that is working has about a 6 foot long cable gong from the classic to the 4 port switch.

That's all I can think of. Just lucky the classic on port 502 (that works rock solid) is the one with the WBJR connected so when i loose remote communication with the other classic I can at least see its functioning by watching the input Amps via WBJR.

I will try and dig up a longer (say 9 foot) cable tomorrow and see if that makes it stable.

Kurt

[Westbranch]

I have a similar setup, 2 classics BOTH on port 502, just change the last number before the 502....195,168,1, 22 or 33, 502....works like a dream...

[zoneblue]

I also cant think of a reason to change the port. The port forwarding from the WAN side shouldnt need it. Forward both IPs:502 through.

There certainly was advice here previously to use short ethernet leads, however my testing from 300mm to 10m it made zero difference.

[offgridQLD]

"I have a similar setup, 2 classics BOTH on port 502, just change the last number before the 502....195,168,1, 22 or 33, 502....works like a dream..."

I can't change the that as I am not accessing them via my local network I'd . my internet conection is a static IP so I can just access it via my static IP number and port for each divice.

It's a funny one as it worked well for a long time and works intermittently now.

Its not the cable tested a longer one.

Kurt

[offgridQLD]

As you can see below I just tried connecting to the local app 2 min ago and now it's working on both classics. So that just shows it works and has done in the past for some time configered as it is.

Just that I'm 99% confident to say the classic on port 503 will drop out if I let it be for a little while as this is what was happening all week. Classic on 502 solid green light all day and classic on port 503  drops in and out (more out than in ) and I cant tell why.



Kurt

[TomW]

Does this happen when you use your local network address for the Classics on your local network?

If it only does it from your internet IP then it could be the router is being twitchy?

I never used mine via a static internet IP just my local network so no experience with that.

Just tossing it on the wall to see what sticks.

Tom

[offgridQLD]

Tom,
        No once it disconnects it wont connect via local  as well.  Anyhow 99% of my need for the local app is to log on from another house remote connection. If its the router its funny how it would only play funny business with port 503 and not 502.

Connection lasted about 1hr and now this Intermittent disconnects on just one of the two controllers is frustrating particularly when it was solid for months.




Kurt

[zoneblue]

Mate you have both classics with the same ip address!. No network can have two devices on the same network with the same ip address.  They must be unique. The fact that it may work is not a reason to do it. Switches will try their best obviously, but its going to be unpredictable

[offgridQLD]

They don't have the same Ip address. your mixing up local ip address with my static ip address to the outside world.


192.168.1.102is the local ip address of the classic on port 503

192.168.1.106 is the local ip address of the classic on port 502

As I mentioned before I have a STATIC IP ADDRESS for my outside connections. (most people have a dynamic ip address) So I can remotely assess any device on my local network just by typing in my (static IP address) and the port number that is forwarded to that device by my router that knows what loacal IP  address to find it on as its associated with that port (as part of the post forwarding) .

So no I don't have two classic on the same IP address I have One static Ip to the outside world and lots of local IP's and ports to connect to .

I hope that clears things up.

Anyhow even using the local network Ip directly doesn't pick up the 2nd classic as you can see below.


Kurt

[zoneblue]

Ok, my mistake. Youre using different ports because the router can only port forward to different IPs using differnet ports.

Not sure i can help, the classic network issues were reportedly fixed last firmware update, however i have not had a chance to test this exhaustively.

[offgridQLD]

It cold still be something funky going on in my router I'm not ruling it out.

I have all the latest firmware in both classics to to rule that out.

I thought I was on top of all this with such a good run for so long.

[toothy]

Amazing timing Kurt,

A few days ago I took a Classic 250 out of my 3 Classic system and replaced it with a 200, it gave me fits, firmware not taking and little lock-ups and the like. I got that sorted out.

I read a post from Midnite/Andrew about a long Ethernet cable being bad between Classic and switch and made a short one and all seemed well for a while. Now the 2 classics that have longer cables and have worked perfectly for a long time stopped working but the new one was showing up and working great.

Now to the point, I presently have 2 totally separate internet connections, old router 1 and new router 2. I switched routers earlier today from #1 to #2 and all showed up and looked good, then tonight the issue.

I plugged it back into the #1 router and all seems to work with no change other than switching routers and Wi-Fi connections. They had been on the #1 router for years and I have only tried them on the #2 that had the issue a few times in the last week but all seemed well.

So I believe there is something to this router/Classic not playing together business.

I'll let you know if router #1 that has worked for years has any issues in the next few days, I will probably not be able to help myself and will try #2 again. Not to make this anymore convoluted but router #3 that will take the place of #1&2 will be here next week.

Thanks for the post, I wouldn't have tried switching routers until this popped up as the first post, exactly when I needed it.

Thanks
Wade

[toothy]

OOOP's

My stability has been overstated!

I wrote to soon, now I'm getting "device not available" on the old #1 router from one Classic.

Wade

[offgridQLD]

Well I didn't touch anything just drove 100km to the other house and pulled out the laptop .

Connected up fine remotely straight away. This is after it wouldn't connect all afternoon then I was on location.

Will see how stable it is.  

You know working sometimes is worse than not working at all.


Keep us posted

Kurt

[dgd]

Well I didn't touch anything just drove 100km to the other house and pulled out the laptop .

Connected up fine remotely straight away. This is after it wouldn't connect all afternoon then I was on location.

So you are sure its not a problem with the Local App?
When you see that a Classic is not found (Device not available) have you tried closing the App, restarting the laptop, then restarting the App?
Closing the App my not be sufficient as there may be a temporary lock file that is not clearing properly hence the need to restart the laptop.

dgd