Same switch location needed on static IP?
-
Even if I encountered this before (on some devices fior wich the manufacturer mentioned this), I was a little surprised in this case: when tried to connect through DWC to 6XD board, with static IP, on Ethernet LAN, it was not possible to do this but only if the board and the computer where under the same switch.
As only one LAN connector is available in the close proximity of the printer, I used a switch to connect the board and a laptop to it. It works very well.
BUT: when trying to connect from a remote computer, being on the main switch, wich of course it is ”before” that auxiliary switch, I could not acces the board.
Connecting the board directly the main switch (removing the auxiliary switch, that is...) solved the problem.
I did not tried with DHCP though, maybe it is a known network issue, but as I am not a networking experienced guy, I really cant tell but testing, and have not done it yet.
-
Perhaps the port on the aux switch that you used to connect to the main switch was defective?
When the computer was connected directly to the aux switch, and the aux switch was connected to the main switch, could you connect to things on the main switch?
Is the aux switch a managed switch? Does it have a web interface for configuring the switch?
Frederick
-
@fcwilt No, the switch is ok.
Yes, I could connect through the AUX switch to the things in the main switch.
No, AUX switch is not a managed switch, as far as I know, so no separation was set in it. The main switch is a managed switch, though, but there are no such separations between resources (small company, low paranoia level, hehe ...).
I can connect through other AUX switches, for example from a computer on an AUX switch to a printer or a computer on another AUX switch. Some of them has DHCP enabled, some of them static IPs.
It may be the implementation on the DX6 somewhat limited, as it may be the case in other embedded devices, I could not say anything about this.
Also, as I mentioned, some device manufacturers mentioned this, but please do not ask me know who. If I recall right (and I am pretty sure I do, when I worked with some TIBBO boards, there it was the same situation, that the board and the computer (at least when programming it), to be on the same network ... tier (same switch for example).
I will test with DHCP, while this is not so important, as for many such devices (like in ... small printer farms), it is most probably that they will work with static IPs and shared switches. -
The issue is not likely to be with the Duet.
I have Duet 2, Duet3 gear on the ground floor and I can access all of it from my office computer on the 1st floor which has to traverse 4 switches to reach the printer.
Never had any problems.
Using or not using DHCP would normally not be a problem unless there was a conflict between your static address and a dynamic one from the DHCP server.
Are all of the devices (computer and printer) on the same subnet? Are there any virtual networks created by the managed switch?
Frederick
-
@fcwilt Yes, they are on the same subnet. I simply add or remove the AUX unmanaged switch, and no, no other virtual network created. Even if they would be, the port where I am adding or removing the switch stays the same, so it would be on the same virtual network, if that would be the case, wich it is not.
I mentioned that strange mention of the TIBBO boards (maybe you are not familiar with) of the same tier need, on the network, as like DX6, the protocols/management is an embedded software, and I think that some constraints may manifest in the drivers. A simple supposition.
On DHCP, if you have a conflict, it will not work at all, but if it works on different tiers, then... it works. I will test this, this month, and let you know.
And anyway, knowing of this behaviour, may help others too, but I do not see this as a problem. Maybe somebody more knowledged in networking will investigate and let us know the results.
I alșo will try another switch, with first occasion, however, right now, I think this was the last free switch in the house. Maybe it is there a problem, as this one is a small old 10/100 CISCO.Al the best,
Paul -
