Server not found

My Problem:
When I click 'Media Server' on the TV I get a "Server not Found" message.
I can access the internet using the TV 'Viera Cast' button so the wireless network must be OK.

My hardware
I have a Panasonic TH-P42V20Z with a Netgear WNDA3100v2 wireless network adaptor.
My PC runs Serviio under XP and has a Linksys WRT120N wireless router.
I have a Dynalink RTA1320 broadband modem.

Other information
The PC can access the internet without problems.

The Media Server used to work some months ago until the Netgear adaptor failed and has since been replaced. Since then, I may have made setup changes to the Linksys router.

I don't know where to start to analyse and fix the problem, any help would be appreciated.

Bill

[zip]

this has been discussed here many times. The router is probably giving you a new IP address, make sure you are not binding to the old one.

Thanks Zip for your reply. This is not the problem. The Bound IP is the same as the PC running Serviio. I have also opened up TCP port 8895 and UDP 1900 on the router by enabling Single Port Forwarding for Serviio (I guess this is the correct action). Delayed start of the service does not seem to be the problem as the get the same Server not Found message after stopping and re-starting the service.

I have searched the forum for "Server not Found" and only found one set of posts that also cover the same checks that I have done in this post.

Bill

[moltra]

Can you post your serviio.log file and the IP addresses of your devices.

Did you do any changes or updates to anything?

I have attached my serviio status screen:

Serviio.jpg (53.08 KiB) Viewed 21980 times

serviio.log:

serviio.log

(205.41 KiB) Downloaded 833 times

My IP addresses are:
PC 192.168.0.100
Modem 192.168.1.1
Wireless router 192.168.0.1
Panasonic TV 192.168.0.101

Serviio bound IP 192.168.0.100

I don't know if I have made any significant changes, it was > 6 months ago that Serviio was working and the known changes since then are detailed in my first post.

[moltra]

check your panasonic tv and see if the IP address has been changed. it might have received and update and the ip address changed.
I do not see anything in the log showing it seeing the 192.168.0.101 renderer at all.

Unplug your router and TV and wait for about 5 minutes then plug back in to reset both devices. and see if they connect.

Thank you moltra for your efforts. The TV is still saying "Server not Found". I tried to power off both TV & router. The TV IP address acquisition is set to auto and it has automatically found 192.168.0.100 (the Serviio bound address). The TV can be set to do a connection test which succeeds including:
Check acquired IP address
Check server connection

BTW I can ping the TV from the PC (192.168.0.101).

I am away for 3 days so may not immediately respond to any more replies.
Bill

[moltra]

The TV and computer cannot be on same ip address

Sent from my DROID RAZR using Tapatalk 2

From my computer (192.168.0.100) I can ping the TV on 192.168.0.101.

Hi, I'm having similar problems ... except it is intermittent. Although to be honest it is more that intermittently it works. Have tried all day to day with no success - but mid week it was fine.

I'm not very techy but some things to note:
- the TV is a Panansonic Viera DT30 and I am using the "Viera" profile
- the lights are green (for the TV) on the 'status' page
- but, all day today if I try and find a DNLA server on the TV (using the home network menu) it says one doesn't exist
- running ipconfig gives the following (info re media state looks worrying !!!)

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : home

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : home

Tunnel adapter Local Area Connection* 9:

Any help would be appreciated, because it is great when it works .... Thanks ... Steve

[zip]

are you on wifi or wired connection? If wifi, check the signal strength. If wired we've seen similar issues when people used poor routers on their network.

Zip,

My setup is as follows:

Laptop wifi to BT Homehub 2 router - about 1 foot away and excellent signal strength. TV (and PVR and Blueray player) wire connected to router via Netgear (200) homeplug adapters. I actually tried connecting my laptop to the router via wire yesterday, but it didn't improve the situation !

Today all has been sweet - everything working seamlessly - but I haven't changed anything !!!!!

This network works fine (all the time) for internet access (not via laptop) eg BBC iPlayer on both PVR and TV.

Thanks ...

Update this morning .... can't get it to work again !

Hi steveaj, zip & moltra

When my serviio was working it was a bit intermittent. When I would attempt to connect the TV the the media server it would come up with "server not found" immediately. But if I left it for a minute or 2 its would connect ok.

ipconfig gives me:
Host Name . . . . . . . . . . . . : home-q6l4g6cg7q
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : home

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : VIA Compatable Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-E0-4C-9F-13-9A
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 203.96.16.35
203.96.16.36
Lease Obtained. . . . . . . . . . : Monday, 11 June 2012 8:23:03 p.m.
Lease Expires . . . . . . . . . . : Tuesday, 12 June 2012 8:23:03 p.m.

I dont see 'media state' as steveaj does.

What else can I do to analyse the problem?

[zip]

I read the BT router was causing problems for other ;-(

I have fixed the problem after several days of troubleshooting. The main problem was my Eset firewall was blocking.

I also pleased to say that mine has been working quite seamlessly for a while now .... both with 0.6 and 1.0.1. Not knowlingly done anything to fix it though. Hoping I am not testing fate by making this statement !