What make and model is your master router? Its' actual device mapping capabilities may be minimal with limited accuracy and thoroughness. Plus any network misconfigurations can cause misleading or confusing results....
All I can think of, for the moment, is that 1) the ground floor computer is mis-configured for your network and/or 2) the second floor router is likewise misconfigured.
The mis-behaving ground floor computer is looking for an IP address. You configured its' network adapter to look for the master router at 192.168..
For some reason ground floor computer is finding the second floor router instead of the master router.
But I am also wondering about the physical wiring - are you sure that the ground floor computer is truly connected to the desired router (ground floor router). Double check the LAN to LAN connections.
What, if anything, is on the floor between the two. Is there some rogue router involved - maybe on the floor between? Any switches that you know of? What network name do you expect and what is the "another network name"?
Did you ever use that "another network" name: wired or wireless? What about Windows Workgroup? Have you used that?
Sketch a network diagram per my earlier suggestion. Lable all devices, their host name, current IP (assigned or static),subnet mask, MAC, network name, etc..
I think the key is to get a "big picture" view of your network. Compare what you expect to what is and the comparision should narrow down the problem.
For example:
It could be expected that your master router is configured to be IP 192.168.1.1 and the four other routers would be statically configured using 192.168.1.2, 192.168.1.3, 192.168.1.4, and 192.168.1.5. (E.g., a Linksys environment...) via the LAN to LAN connection ports.
Verify that any main router reserved static IP's are being associated with the correct device MAC. Especially for the routers.
And the master router would be permitted to issue a DHCP IP address range from 192.168.1.10 to 192.168.1.20 (All subnet masks being 255.255.255.0.)
The objective is to verify that current configuration does indeed map to your expectations/requirements.