Windows 10: How to detect LAN item; not recognised by DHCP

I have a LAN device that I want to connect to my computer. (It is an interface between my model railway and my computer which has the software to operate it).

I plug in the Ethernet cable and the port on the device lights up, the hub to which it is attached also lights up and for a few seconds the amber light on the port flashes. Then things settle down and the amber (polling?) light blips every few seconds. I am not that experienced in these matters but that all seems sensible to me.

However, I cannot 'see' the device on the network. I have logged on to my router and found the DHCP table and nothing changes when I plug/unplug the Ethernet cable from the device. Nor can I access the factory set IP address of the device. I have tried DOS and the 'arp' command but nowhere can I see the device.

Am I not doing something that I should? I would welcome any insight as to why I cannot see the device given its apparent recognition.

:)

 

Nokia E65 Wlan Problem

In the WAN, are you using DHCP or PPPoE? Set the LAN to DHCP enabled. Don't use MAC filtering in Access Control.

Gembird - world leader in the production of computer hardware

 

wifi problem on nokia 5800

(Give me the url of your Uni. The LAN of your lap should be DHCP in the adapter settings. If the Uni has given you a static IP, use it instead of DHCP. The WLAN of your lap should be given a static IP in the range of the LAN for the phone. The phone
itself can be DHCP. The proxy should be set in the LAN of the lap. Can you follow?[/i])





url of uni is http://bhu.ac.in

DHCP is disabled in the lan's adapter settings.

I have a static ip.I entered it manually in the ipv4 settings of lan.Proxy is set on the lan .

The whole problem is that the WLAN is not given an ip in the range of lan..

Should i try bridging the connections instead of ICS?Or is there some other solution?

 

Hi ALANGR

Might be helpful for everyone if you stated make and model of device you are trying to connect for this railway.

Next could you better describe LAN. You have a modem and router or a modem/router. Your PC connects to....

The railway connect to a hub and that hub (I think you mean Switch) is then connected to router?

Has anything changed in environment, like new router or a router reset. Have you check you laptop network, is it set to Private or Public?

Was Windows recently updated or maybe a better questions, when did this last work?

Have you tried disabling PC firewall(s) and pinging IP address of device? cmd prompt Ping 192.168.1.10 (using your address range?


Ken

 

In order to initially set up the device, you might have to set your computer to a static IP address that is in the same subnet as the factory IP address of the device. For example, if the factory IP address of the device is 192.168.0.115, you would set your computer for 192.168.0.10 for example. 192.168.0.xx would be in the same subnet. Then using only the hub not connected to anything else, connect only the computer and the device to the hub. No other connections. Then see if you can ping and communicate with the device via it's factory set IP address.

 

Hi Ken

Details: the device is a Lenz 23151 connector that sits between a W10 computer and a Lenz Digital plus system via ‘expressnet’. The LAN has a modem/router (Speedport Entry 2i from Cosmote, my ISP in Greece). I then have 4 Apple airport express WiFi stations (1 base and 3 extenders) to cover a two-story house and a basement (where my model railway is situated). The Airport Express in the basement goes to a hub/switch and then to a W10 computer that runs the software for the train control and also to the 23151 device which is also connected to the Lenz computer system.

Nothing has changed lately in this setup and I cannot ping the device (no response, timed out).

NavyLCDR

I followed your suggestions and then I could ping my device OK. However, when re-setting the (local) computer back to its ‘use DHCP’, I was again unable to communicate. The factory set IP address of the device is 192.168.0.200 and all my other network items have addresses 192.168.1.xxx. I am guessing that this may be the root of the connection problem and, if so, I am looking either to change the IP address of my device to 192.168.1.200 or to do something to change way the DHCP allocation of addresses in my router/modem works.

I also tried setting my computer to 192.168.0.10 in the hope of moving forwards but this messed up my internet access and W10 sorted this out by setting me back to DHCP again.

I may be off on a wrong idea here but I would appreciate a way to tidy up this problem.

 

The basic issue here is you have two SubNets, I think - we'll call them 192.168.0.x and 192.168.1.x, which by the nature of networking will not communicate with each other. this explanation can only be used as a guide as we are missing Vital information in regards to actual IP addresses used

You have two possible ways to get this sorted out, you either need to add a router into the system to "translate" between the two subnets,






or you can combine the two subnets into one, (This is the best option IMHO).

Decide which of the subnets are easier to re-assign, I would suggest that the Internet connected subnet is the easiest, as I do not know the workings of the Lenz 23151

You will need the manual for your router, and any airport devices (if these are set-up manually).

You need to reset your router IP to an address in the same range as the Windows 10 Railway controller PC connected to the Lenz 23151 we'll call this RCPC

Check the IP address of this RCPC and you then need to set the router IP address to an address in the same range, suggest 192.168.n.1 where n is the number in the RCPC and also set the router DHCP to the same range

EG if the RCPC has a preset of 192.168.1.200 the Router would need to be set to (I suggest to prevent clashes), 192.168.1.1 and the DHCP range to 192.168.1.1 to 192.168.1.199. This will leave you a number of addresses that can if needed be set manually as the system changes/grows any (IP address from 192.168.1.201 to 192.168.1.255)

These are just suggestions / examples as I do not know the amount of customisation possible with the components of your system if the Lenz 23151 has to have the controlling PC in a certain subnet range or even a specific IP address then this is the controlling factor in how you set up your other components.

If you need more specific assistance I would need more specific data such as the IP settings of the RCPC and the router

In the spirit of learning there is an explanation of IP and Subnetting here (I apologise for the title which follows the book series) this is only for completeness and I'm sure that If you can give us specifics of your system currently the rest will be easy to do

 

Many thanks for this! I can see what you are saying and need to get to work with the Router manual, etc. and see if I can do it!

I will let you know how I get on.

Alan

 

Most devices you can change the IP they use to what ever you want. The other option is to use the route Cmd in Windows to set a route to the device

 

Hi Alan you are on the right track but something changed as these are now two different subnets.

The route of changing your router IP range is likely the easiest, one they even talk about in manual.

The process to change your Lenz device is also outlined in manual. Starting on page 5.

http://www.lenzusa.com/1newsite1/Man...net_Config.pdf

Ken

 

I am descending into unknown areas and while I can see the implication of two different subnets, I am concerned about doing something unintended that will lock me out from the internet!

The DHCP table in my router looks like this with apologies for the formatting:

DHCP server On

LAN IP address 192.168. 1. 1

Sub-net mask 255.255.255. 0

DHCP start address 192.168. 1. 2

DHCP end address 192.168. 1.254

It then goes on to indicate that the ISP DNS is off.

A simple question is whether I can change the DNS server table to something like

DHCP server On

LAN IP address 192.168. 0. 1

Sub-net mask 255.255.255. 0

DHCP start address 192.168. 0. 2

DHCP end address 192.168. 1.150

Is this what you are suggesting, Barman58? This would seem to leave my device (192.168.0.200) clear of the DNS allocated addresses but would this leave the system running OK and allocate 192.168.0.xxx to all my other networked items? Or have I missed something important?

Thank you, all.

Alan

 

Alan, that should work without any issues,
I suggested that you reduce the DHCP range as I was not certain of the way that the Apple devices were set up, if they are currently set manually you should use addresses outside the DHCP range if not then leave them as is - it's actually quite normal to manually assign IP addresses for "Network Infrastructure devices" such as extenders and sub routers as these are better found if the IP is fixed.

If the extenders are manually set for IP, (back to the Airport Router), then you need to bear this in mind and allocate IPs from the non DHCP range

I personally tend to use pre allocated DHCP IP addressing, which forces the IP through DHCP, rather that manual method, as this gives me better centralised control, (single change of the router settings changes everything without having to change individual items) - but I digress manual allocation is simple enough to do in a home network rather than the systems I have worked with where you can have hundreds or thousands of devices

 

Thanks, Nigel

I will go ahead; it will probably be tonight after all users are off the LAN; so I will see what tomorrow brings!

Thanks

Alan

 

We'll be here if you notice anything that's not been mentioned, But hopefully all will go smoothly *Smile

 

OK, all done and dusted, I think. I was worried at first because I could not get onto the net but it took a few minutes to settle down. All the Apple devices have been rebooted along with the PCs and I can now see my device along with everything else. I have not actually connected to use the device yet, that will be tomorrow - but all points to a successful situation.

I am most grateful to you (all) for your help/comments and especially to NavyLCDR for getting to the root of the problem and Nigel for the detailed blow-by-blow support.

I will, of course!, comment if anything untoward happens tomorrow.

Thanks all

Alan