xschedule web interface

[smithbuilt]

How can I find the IP address of the xschedule web interface? I just added a second NIC and forced the show to 192.168.1.5. My home network is x.x.2.x. Previously I cold access xschedule at 192.168.1.109 but not since I added the new card. Where should I find it on.1.x or .2.x? I can access it from xschedule but it shows 'http://localhost/xScheduleWeb/index.html?page=home'. I want to be able to access this on an android device, which I could before. I can't remember how I figured out the  .1.109 before, that was a couple of years ago

[keithsw1111]

You should be able to use any up address on that machine that is on the same network as your phone.

[smithbuilt]

Im sure I must be missing something simple but for the life of me I cant get this.
on my phone when I am on the 192.168.1.x network, if I enter 192.168.1.109 I don't get anything.
If I'm on the 192.168.2.x network, same thing. On the desktop running xschedule, using Edge or chrome if I try 192.168.1.109 or 192.168.2.109, is get nothing. From xschedule the page shows up. From an article I read about 'localhost' I tried 127.0.0.1 on the desktop and I get xschedule. But that doesn't work on the phone. I tried changing the web server port ( in options) to 81 and 8080 but still nothing. I can access the Falcon boards on both the desktop and phone.
 I am assuming that x.109 is the correct location, if it can be set differently, how do I do that?
I went to Win10 firewall settings and set all versions of xschedule to both public and private network and still nothing
Please, what am I missing? right now I'm happy with looking like an idiot for missing something easy.

Thank you

[Gilrock]

What do you mean you are assuming x.109 is the correct location?  Only the IP address of the computer running xScheduler is the correct location.  Run a DOS prompt and type "ipconfig /all" and scroll up to the ethernet adapter and see what IP address it's grabbing.

[smithbuilt]

OK Thank you Gilrock. That has me there. I didn't understand that the access was through the IP of the computer itself. Now I can access the web interface from the actual computer at both the .1.x network and the .2.x network using the IP setting for each NIC. Thank you so much!!!