192.168.49.1 address when installed on Nvidia Shield

[billcook 0]

Possible new user here (though it's not looking likely if this is how the install goes).

 

I have an Nvidia Shield with a DHCP reserved address of 192.168.1.6. I have reserved addresses for everything on my LAN but otherwise it's a standard 192.168..1.* DHCP home setup.

 

I installed Emby. It tells me it's at 192.168.49.1:8096.

 

I cannot reach this from:

 

1. A web browser on the Shield using localhost:8096, which the server tries to send me to.

2. A web browser on the Shield using 192.168.49.1:8096.

3. A web browser on the Shield using 192.168.1.6:8096.

4. A web browser on my laptop using either address.

 

The Emby app i installed on the Shield connects to the server but I can't do anything, because the server, I presume, needs to be configured.

 

I saw one other post in the forum where someone had the same problem but they were able to connect using their version of the 1.6 address.

 

Nothing is plugged into the Shield, so that address is presumably a virtual NIC, but I can't do much about that.

 

What's the solution?

[GrimReaper 4739]

Was just reading similar post few minutes back. Is your Shield connected to your router wired or wireless?

[billcook 0]

Wireless (though it's normally wired).

 

I'm not sure why that should matter, except maybe that's how that virtual NIC is showing up.

 

Any specific suggestion? Otherwise, I think I'll uninstall the server, plug back into the router and start over.

 

Thanks!

[nyplayer 90]

Possible new user here (though it's not looking likely if this is how the install goes).

 

I have an Nvidia Shield with a DHCP reserved address of 192.168.1.6. I have reserved addresses for everything on my LAN but otherwise it's a standard 192.168..1.* DHCP home setup.

 

I installed Emby. It tells me it's at 192.168.49.1:8096.

 

I cannot reach this from:

 

1. A web browser on the Shield using localhost:8096, which the server tries to send me to.

2. A web browser on the Shield using 192.168.49.1:8096.

3. A web browser on the Shield using 192.168.1.6:8096.

4. A web browser on my laptop using either address.

 

The Emby app i installed on the Shield connects to the server but I can't do anything, because the server, I presume, needs to be configured.

 

I saw one other post in the forum where someone had the same problem but they were able to connect using their version of the 1.6 address.

 

Nothing is plugged into the Shield, so that address is presumably a virtual NIC, but I can't do much about that.

 

What's the solution?

 

On settings advanced bind to the correct local IP address.

Edited April 27, 2019 by nyplayer

[GrimReaper 4739]

On settings advanced bind to the correct local IP address.

He cannot access the server through the browser interface, hence no settings available.

[GrimReaper 4739]

The Emby app i installed on the Shield connects to the server but I can't do anything, because the server, I presume, needs to be configured.

What do you mean by that? Do you get to the login screen or what?

[nyplayer 90]

What do you mean by that? Do you get to the login screen or what?

 

Just get the local IP of the Shield then http://shieldIP:8096 . go into network setting on the shield and get the right IP. Once in the settings you can bind to the correct address.

Edited April 27, 2019 by nyplayer

[nyplayer 90]

He cannot access the server through the browser interface, hence no settings available.

 

Yes he can by getting the corret shield IP.... from the shield network settings.

[GrimReaper 4739]

Wireless (though it's normally wired).

 

I'm not sure why that should matter, except maybe that's how that virtual NIC is showing up.

Beacause ppl tend to overlook that setting static IP on Shield is separately done for Ethernet and WiFi networks:

IP setting that jumps into your face once you go into Settings>Network is Ethernet only and it does not carry over for any WiFi network. To do that, you need to click that particular WiFi network you are connected to and change IP settings from DHCP to Static there.

Edited April 27, 2019 by GrimReaper76

[GrimReaper 4739]

Yes he can by getting the corret shield IP.... from the shield network settings.

Well, if he states:

I cannot reach this from:

 

 

 

1. A web browser on the Shield using localhost:8096, which the server tries to send me to.

 

2. A web browser on the Shield using 192.168.49.1:8096.

 

3. A web browser on the Shield using 192.168.1.6:8096.

 

4. A web browser on my laptop using either address.

 

I don't see which other IP he could try.

[nyplayer 90]

Well, if he states:

I cannot reach this from:

 

 

 

1. A web browser on the Shield using localhost:8096, which the server tries to send me to.

 

2. A web browser on the Shield using 192.168.49.1:8096.

 

3. A web browser on the Shield using 192.168.1.6:8096.

 

4. A web browser on my laptop using either address.

 

I don't see which other IP he could try.

 

All he has to do is look in the Shield network settings and you will see the IP.

 

Edited April 27, 2019 by nyplayer

[GrimReaper 4739]

All he has to do is look in the Shield network settings and you will see the IP.

Quote

I have an Nvidia Shield with a DHCP reserved address of 192.168.1.6. I have reserved addresses for everything on my LAN but otherwise it's a standard 192.168..1.* DHCP home setup.

Unquote

 

Well, I'd guess it's .6, basis above.

Edited April 27, 2019 by GrimReaper76

[billcook 0]

What do you mean by that? Do you get to the login screen or what?

--> From the Shield client app, yes, I get in the app. There's no media, there's no way to change server settings, etc.

 

 

Beacause ppl tend to overlook that setting static IP on Shield is separately done for Ethernet and WiFi networks:

--> I do not set a static IP on the Shield. I reserve an address in DHCP based on the MAC address of each device. This applies to both wired and wireless.

 

 

Just get the local IP of the Shield then http://shieldIP:8096 . go into network setting on the shield and get the right IP. Once in the settings you can bind to the correct address.

--> The local IP of the Shield is 192.168.1.6. Going to http://192.168.1.6:8096 gets me...not found.

 

(Sorry, I'd try to format this better, but this is a bit of a wacky interface).

[nyplayer 90]

What do you mean by that? Do you get to the login screen or what?

--> From the Shield client app, yes, I get in the app. There's no media, there's no way to change server settings, etc.

 

 

Beacause ppl tend to overlook that setting static IP on Shield is separately done for Ethernet and WiFi networks:

--> I do not set a static IP on the Shield. I reserve an address in DHCP based on the MAC address of each device. This applies to both wired and wireless.

 

 

Just get the local IP of the Shield then http://shieldIP:8096 . go into network setting on the shield and get the right IP. Once in the settings you can bind to the correct address.

--> The local IP of the Shield is 192.168.1.6. Going to http://192.168.1.6:8096 gets me...not found.

 

(Sorry, I'd try to format this better, but this is a bit of a wacky interface).

 

Did you make sure the EMBY server is started on the Shield ? You can go to APPS on the Shield and start if necessary.

[nyplayer 90]

Quote

I have an Nvidia Shield with a DHCP reserved address of 192.168.1.6. I have reserved addresses for everything on my LAN but otherwise it's a standard 192.168..1.* DHCP home setup.

Unquote

 

Well, I'd guess it's .6, basis above.

 

You right maybe the server is stopped.

[billcook 0]

I was going to say yes, but I guess I really only know that it's enabled.

 

I'll check that. In the morning though.

 

Thank you for the suggestions.

[GrimReaper 4739]

You right maybe the server is stopped.

We'll see in the morning.

 

Cheers, m8.

[GrimReaper 4739]

--> I do not set a static IP on the Shield. I reserve an address in DHCP based on the MAC address of each device. This applies to both wired and wireless.

I've long since left the road of DHCP reservations as one of my old router's firmware was giving me a headache. So, I set static IP on each of my devices (not that I have them that much ) separately and keep them out of router's DHCP server IP pool. Guess old habits die hard. Anyway, out of curiosity, I'd suggest you set your address ON the Shield - it takes literally 20-30 seconds, restart Shield (if your Emby server is Enabled it will boot up as well) and then check what is server page showing as IP.

 

Cheers

Edited April 28, 2019 by GrimReaper76

[billcook 0]

Got it working...thanks for the pointers.

 

I don't know for sure, but I suspect the server was not running properly. I tried it first thing without making any changes--no go. I disabled and re-enabled the server (which is apparently as stop/start) and though it seemed to take some time to become available, I was able to log right in at 192.168.1.6:8096. Of course, the 192.168.49.1.:8096 still fails.

 

That bad mapping is most definitely a bug in the install process. I currently use Plex; although it sees that other IP address (I checked ito ut). I think it defaults to a 192.168.x.x address if available. But regardless, it lets you pick the correct one in a list in settings.

 

So, I think I'm good. I'll play with this over the next week or two. Like I said, I currently use Plex (that's why I have the Shield) but it really just gives me a headache. I'm hoping Emby will be a better experience. I will say that Plex is phenomenal when it works. I just don't have the time or interest in the care and feeding it seems to require.

 

Thanks again for the help getting started!

Edited April 28, 2019 by billcook

[GrimReaper 4739]

Got it working...thanks for the pointers.

 

I don't know for sure, but I suspect the server was not running properly. I tried it first thing without making any changes--no go. I disabled and re-enabled the server (which is apparently as stop/start) and though it seemed to take some time to become available, I was able to log right in at 192.168.1.6:8096. Of course, the 192.168.49.1.:8096 still fails.

 

That bad mapping is most definitely a bug in the install process. I currently use Plex; although it sees that other IP address (I checked ito ut). I think it defaults to a 192.168.x.x address if available. But regardless, it lets you pick the correct one in a list in settings.

 

So, I think I'm good. I'll play with this over the next week or two. Like I said, I currently use Plex (that's why I have the Shield) but it really just gives me a headache. I'm hoping Emby will be a better experience. I will say that Plex is phenomenal when it works. I just don't have the time or interest in the care and feeding it seems to required.

 

Thanks again for the help getting started!

Glad you sorted it out. I'm sure you'll quite soon forget about Plex and wonder Why oh why didn't I do this sooner.

One thing to keep in mind, tho: As stated in the first post once you get here, Android Server is still in BETA so occasional hiccup might be expected every now and then, although my server's been running for months without any issue whatsoever, literally maintenance (and frustration) free.

 

Cheers

[billcook 0]

Here's hoping!

 

Good tip on the Android TV server. Honestly didn't do much research here; just (finally?) got wind of Emby as a viable alternative and rushed on over.

 

Thanks again for the help.

[Luke 42077]

If the wrong local ip address is detected you can always customize it in advanced server settings with the bind to local address setting.

[billcook 0]

Well, yes. But only after being able to connect, which was the original issue. But thank you for the reply!

[Luke 42077]

 

 

1. A web browser on the Shield using localhost:8096, which the server tries to send me to.

This really should work and i've never seen this be a problem before. What browser do you have on the Shield?

[billcook 0]

You'll see above that the server was not properly started which is why it didn't work.

 

But thanks for the input...