Local hostname doesn't work & cache location

[denywinarto 5]

Hi, i got 2 issues 

 

1. I need clients to be able to access locally via server's hostname,

right now on clients it only works via server's ip address.

I double checked and and type hostname on cmd and the hostname is correct.

It's also the same as the one showing on dashboard  

Client and server also has SMB connection, and the SMB can use the hostname without issue.

2. I run emby portable from another drive, but

Cache location seems to be always reverted to userdata upon reboot?

I'm pretty sure i changed it few days ago, but this morning it seems to be back to the default %userdata%

[pwhodges 2014]

Is the server's name defined in a DNS somewhere?

Paul

[denywinarto 5]

1 hour ago, pwhodges said:

Is the server's name defined in a DNS somewhere?

Paul

By DNS are you referring to emby's setting?

I cannot find settings that related to this. 

[Carlo 4561]

Hi, he was referring to Domain Name System and the DNS entries are what you use to control the names of computers for domain names.
That is how things could be setup if you want to access your Emby server from the Internet.

If you're simply wanting to access your Emby server by name on your LAN you should be able to do that as well.  For example my main server is named "EMBYSERVER" so I can use that name in the apps or can open Emby in a browser using http://embyserver:8096 on windows (not case sensitive).

For that to work you should be able to open a command prompt on windows and type 

ping servername

if it doesn't time out but gives a response the name will work locally for use by Emby.

[denywinarto 5]

Is it the host file in C:\Windows\System32\drivers\etc ?

It doesnt have entry yet

[Carlo 4561]

Without touching the hosts file you can normally ping all machines by name in your local network running Windows.

[denywinarto 5]

20 hours ago, cayars said:

Without touching the hosts file you can normally ping all machines by name in your local network running Windows.

Just tested this, i am able to ping the hostname from client,

but i cant access it through browser, hostname:8096 or hostname:8920 dont work

Oddly ipaddress:8096 works

[Carlo 4561]

That makes no sense.  Are you using the following format?

http://name:8096

If it doesn't work what error do you get?

Edited November 16, 2020 by cayars

[rbjtech 5284]

Unless the user is running their own local DNS server - then local name resolution without a FQDN will be using NetBios/NetBeui lookup from the 'master' Browser - not DNS - and if that is not functional, then it will be using the ISP's/Global DNS to resolve (which obviously won't have your local IP's ..)   

at a command prompt - use : 

nslookup <your servername>

if this does not resolve to the correct IP, then this is your problem.

You may have set a DNS suffix or something - and may need to use the FQDN (Fully Qualified Domain Name) - ie myserver.local for example for it to resolve.

Also try -

nbtstat -n

This will display all the NetBios/NetBeui hosts available on the local network.

 

 

 

[denywinarto 5]

Thanks guys, it's solved, i'm not sure why it didnt work earlier

http://name:8096

Any thoughts regarding the cache location?

[rbjtech 5284]

check ..\programdata\config\system.xml as that contains the cache path.

[denywinarto 5]

On 11/17/2020 at 7:56 PM, rbjtech said:

check ..\programdata\config\system.xml as that contains the cache path.

Yeah its set to another drive now, i will report it should it change again.

 

Also regarding hostname detection failure, it seems only to happen in android clients.

On windows client it works perfectly. Is this a know bug?