Ok so this is weird (1 Viewer)

RICHARDG

Portal Pro
August 21, 2006
333
3
66
Canada
So I am making good progress.
I have the server working and the remotes on all my MP devices are working. Not sure I am able to blast as yet my stb yet, but one thing at a time.
I am however having trouble with one pc.
It seems that the input service does not seem to connect to the server when it first starts.
If I stop and restart it works fine.
This is what the input service log says.
If anyone has any idea I woul dappreciate it.

cheers

2008-08-24 20:48:45.875000 - Log Opened
2008-08-24 20:48:45.875000 - Input Service, Version=1.4.2.0, Culture=neutral, PublicKeyToken=dc0b77bf2c754d95
2008-08-24 20:48:45.906250 - Info: Starting Input Service ...
2008-08-24 20:48:45.921875 - Info: Process priority set to: Normal
2008-08-24 20:48:47.125000 - Error: System.Net.Sockets.SocketException: No such host is known
at System.Net.Dns.GetAddrInfo(String name)
at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
at System.Net.Dns.GetHostAddresses(String hostNameOrAddress)
at IrssComms.Client.GetIPFromName(String name) in F:\MediaPortal Development\Plugins\IR Server Suite\Common\IrssComms\Client.cs:line 370
at InputService.InputService.StartRelay() in F:\MediaPortal Development\Plugins\IR Server Suite\Input Service\Input Service\InputService.cs:line 701
2008-08-24 20:48:47.140625 - Error: Failed to start in Relay Mode
2008-08-24 20:48:48.531250 - Info: Transmit and Receive plugin started: "Microsoft MCE"
2008-08-24 20:48:48.546875 - Info: Receiver plugin started: "Windows Messages"
2008-08-24 20:48:48.546875 - Info: Input Service started
 

RICHARDG

Portal Pro
August 21, 2006
333
3
66
Canada
Getting closer

Ok so I am getting closer to the answer.
Seems there is a known bug in Windows XP that causes it to not reconnect to network resources after reboot.
I have found work arounds for shared drives. But not for this type of connection.
More looking I guess
 

RICHARDG

Portal Pro
August 21, 2006
333
3
66
Canada
Ok so I came up with a work around.
since Microsoft isn't in a hurry to solve their bug.
I solved the problem by setting the service to start manually, then placed a script in the startup that opens and closes a file on each share.
this makes sure I have connectivity to the network resources, Then I do a net start of the servers.
Bada bing bada boom...she works.
Now off to find more trouble.

Cheers
 

Users who are viewing this thread

Top Bottom