home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Plugins
Schedules Direct US/Canadian/Mexico EPG Plugin (Updated August 2010)
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Paul Jackson" data-source="post: 1136804" data-attributes="member: 152549"><p>I found the tvservice error log reported the following. I think it ma be my problem. The scheduler direct works on a system that has no tuners, attatched to the same network. It does not have this error. Both servers are running the same WIN 7 64 bit. The one that is working is a slower sever (much slower) and basically a near fresh install of windows.</p><p></p><p>[SPOILER="Log File"]</p><p>[code][2015-05-18 08:29:38,335] [Log ] [4 ] [ERROR] - Exception :System.Runtime.Remoting.RemotingException: Remoting configuration failed with the exception 'System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted</p><p> at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)</p><p> at System.Net.Sockets.Socket.Bind(EndPoint localEP)</p><p> at System.Net.Sockets.TcpListener.Start(Int32 backlog)</p><p> at System.Runtime.Remoting.Channels.ExclusiveTcpListener.Start(Boolean exclusiveAddressUse)</p><p> at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.StartListening(Object data)</p><p> at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.SetupChannel()</p><p> at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel..ctor(IDictionary properties, IServerChannelSinkProvider sinkProvider, IAuthorizeRemotingConnection authorizeCallback)</p><p> at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel..ctor(IDictionary properties, IServerChannelSinkProvider sinkProvider)</p><p> --- End of inner exception stack trace ---</p><p> at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)</p><p> at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)</p><p> at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark)</p><p> at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)</p><p> at System.Runtime.Remoting.RemotingConfigHandler.CreateChannelFromConfigEntry(ChannelEntry entry)</p><p> at System.Runtime.Remoting.RemotingConfigHandler.ConfigureChannels(RemotingXmlConfigFileData configData, Boolean ensureSecurity)</p><p> at System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData configData, Boolean ensureSecurity)'.</p><p> at System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData configData, Boolean ensureSecurity)</p><p> at System.Runtime.Remoting.RemotingConfigHandler.DoConfiguration(String filename, Boolean ensureSecurity)</p><p> at System.Runtime.Remoting.RemotingConfiguration.Configure(String filename, Boolean ensureSecurity)</p><p> at TvService.TvServiceThread..ctor()</p><p>[/code]</p><p>[/SPOILER]</p><p></p><p>I would rather avoid doing a full fresh install on the server that doesn't work. There must be some sort of conflict somewhere. Any pointers and helping to figure out where the conflict is would be helpful. I have tried to uninstall completely media portal and make sure all remaining files have been removed. I'm not sure if anything lingers in the registry.</p><p></p><p>here is an netstat -a without the TV service running</p><p>[SPOILER="netstat output"]</p><p>[code]Active Connections</p><p></p><p> Proto Local Address Foreign Address State</p><p> TCP 0.0.0.0:135 Jim-PC:0 LISTENING</p><p> TCP 0.0.0.0:445 Jim-PC:0 LISTENING</p><p> TCP 0.0.0.0:554 Jim-PC:0 LISTENING</p><p> TCP 0.0.0.0:2869 Jim-PC:0 LISTENING</p><p> TCP 0.0.0.0:3306 Jim-PC:0 LISTENING</p><p> TCP 0.0.0.0:5357 Jim-PC:0 LISTENING</p><p> TCP 0.0.0.0:10243 Jim-PC:0 LISTENING</p><p> TCP 0.0.0.0:49152 Jim-PC:0 LISTENING</p><p> TCP 0.0.0.0:49153 Jim-PC:0 LISTENING</p><p> TCP 0.0.0.0:49154 Jim-PC:0 LISTENING</p><p> TCP 0.0.0.0:49155 Jim-PC:0 LISTENING</p><p> TCP 0.0.0.0:49188 Jim-PC:0 LISTENING</p><p> TCP 0.0.0.0:50851 Jim-PC:0 LISTENING</p><p> TCP 0.0.0.0:56756 Jim-PC:0 LISTENING</p><p> TCP 127.0.0.1:1994 Jim-PC:0 LISTENING</p><p> TCP 127.0.0.1:2869 Jim-PC:50791 TIME_WAIT</p><p> TCP 127.0.0.1:2869 Jim-PC:50798 TIME_WAIT</p><p> TCP 127.0.0.1:2869 Jim-PC:50802 TIME_WAIT</p><p> TCP 127.0.0.1:2869 Jim-PC:50808 TIME_WAIT</p><p> TCP 127.0.0.1:2869 Jim-PC:50812 TIME_WAIT</p><p> TCP 127.0.0.1:2869 Jim-PC:50815 TIME_WAIT</p><p> TCP 127.0.0.1:2869 Jim-PC:50833 TIME_WAIT</p><p> TCP 127.0.0.1:2869 Jim-PC:50834 ESTABLISHED</p><p> TCP 127.0.0.1:2869 Jim-PC:50855 TIME_WAIT</p><p> TCP 127.0.0.1:2869 Jim-PC:50860 TIME_WAIT</p><p> TCP 127.0.0.1:2869 Jim-PC:50866 TIME_WAIT</p><p> TCP 127.0.0.1:2869 Jim-PC:50871 TIME_WAIT</p><p> TCP 127.0.0.1:2869 Jim-PC:50875 TIME_WAIT</p><p> TCP 127.0.0.1:5357 Jim-PC:50793 TIME_WAIT</p><p> TCP 127.0.0.1:5357 Jim-PC:50794 TIME_WAIT</p><p> TCP 127.0.0.1:5357 Jim-PC:50822 TIME_WAIT</p><p> TCP 127.0.0.1:5357 Jim-PC:50846 TIME_WAIT</p><p> TCP 127.0.0.1:5357 Jim-PC:50847 TIME_WAIT</p><p> TCP 127.0.0.1:5357 Jim-PC:50849 TIME_WAIT</p><p> TCP 127.0.0.1:5357 Jim-PC:50869 TIME_WAIT</p><p> TCP 127.0.0.1:27015 Jim-PC:0 LISTENING</p><p> TCP 127.0.0.1:50834 Jim-PC:icslap ESTABLISHED</p><p> TCP 127.0.0.1:59243 Jim-PC:0 LISTENING</p><p> TCP 192.168.1.2:139 Jim-PC:0 LISTENING</p><p> TCP 192.168.1.2:2869 192.168.1.1:50313 TIME_WAIT</p><p> TCP 192.168.1.2:2869 192.168.1.1:50316 TIME_WAIT</p><p> TCP 192.168.1.2:2869 192.168.1.1:50319 TIME_WAIT</p><p> TCP 192.168.1.2:2869 192.168.1.1:50322 TIME_WAIT</p><p> TCP 192.168.1.2:2869 192.168.1.1:50325 TIME_WAIT</p><p> TCP 192.168.1.2:2869 192.168.1.1:50328 TIME_WAIT</p><p> TCP 192.168.1.2:2869 192.168.1.1:50331 TIME_WAIT</p><p> TCP 192.168.1.2:2869 192.168.1.1:50334 TIME_WAIT</p><p> TCP 192.168.1.2:2869 192.168.1.1:50337 TIME_WAIT</p><p> TCP 192.168.1.2:2869 192.168.1.1:50340 TIME_WAIT</p><p> TCP 192.168.1.2:2869 192.168.1.1:50343 TIME_WAIT</p><p> TCP 192.168.1.2:2869 192.168.1.1:50346 TIME_WAIT</p><p> TCP 192.168.1.2:2869 192.168.1.1:50349 TIME_WAIT</p><p> TCP 192.168.1.2:2869 192.168.1.1:50352 TIME_WAIT</p><p> TCP 192.168.1.2:2869 192.168.1.1:50355 TIME_WAIT</p><p> TCP 192.168.1.2:2869 192.168.1.1:50358 TIME_WAIT</p><p> TCP 192.168.1.2:2869 192.168.1.1:50361 TIME_WAIT</p><p> TCP 192.168.1.2:2869 192.168.1.1:50364 TIME_WAIT</p><p> TCP 192.168.1.2:2869 192.168.1.1:50367 TIME_WAIT</p><p> TCP 192.168.1.2:2869 192.168.1.1:50370 TIME_WAIT</p><p> TCP 192.168.1.2:2869 192.168.1.1:50373 TIME_WAIT</p><p> TCP 192.168.1.2:2869 192.168.1.1:50374 TIME_WAIT</p><p> TCP 192.168.1.2:2869 192.168.1.1:50376 TIME_WAIT</p><p> TCP 192.168.1.2:5357 192:49381 TIME_WAIT</p><p> TCP 192.168.1.2:50765 Jim-PC:50763 TIME_WAIT</p><p> TCP 192.168.1.2:50780 Jim-PC:50773 TIME_WAIT</p><p> TCP 192.168.1.2:50783 a173-223-204-9:http TIME_WAIT</p><p> TCP 192.168.1.2:50785 a23-56-83-243:http TIME_WAIT</p><p> TCP 192.168.1.2:50788 Jim-PC:50781 TIME_WAIT</p><p> TCP 192.168.1.2:50818 Jim-PC:50781 TIME_WAIT</p><p> TCP 192.168.1.2:50819 192.168.1.1:5431 TIME_WAIT</p><p> TCP 192.168.1.2:50823 a23-209-33-144:http TIME_WAIT</p><p> TCP 192.168.1.2:50824 Jim-PC:50820 TIME_WAIT</p><p> TCP 192.168.1.2:50827 a23-67-242-65:http TIME_WAIT</p><p> TCP 192.168.1.2:50828 Jim-PC:50825 TIME_WAIT</p><p> TCP 192.168.1.2:50829 a23-209-33-144:http TIME_WAIT</p><p> TCP 192.168.1.2:50830 a23-67-242-65:http TIME_WAIT</p><p> TCP 192.168.1.2:50838 192.168.1.1:1780 TIME_WAIT</p><p> TCP 192.168.1.2:50839 192.168.1.1:1780 TIME_WAIT</p><p> TCP 192.168.1.2:50850 Jim-PC:50842 TIME_WAIT</p><p> TCP 192.168.1.2:50856 Jim-PC:50851 TIME_WAIT</p><p> TCP 192.168.1.2:50857 a23-56-83-243:http ESTABLISHED</p><p> TCP 192.168.1.2:50858 a23-67-244-72:http ESTABLISHED</p><p> TCP 192.168.1.2:50863 192.168.1.1:5431 TIME_WAIT</p><p> TCP 192.168.1.2:50867 192.168.1.1:5431 TIME_WAIT</p><p> TCP 192.168.1.2:50868 192.168.1.1:5431 TIME_WAIT</p><p> TCP [::]:135 Jim-PC:0 LISTENING</p><p> TCP [::]:445 Jim-PC:0 LISTENING</p><p> TCP [::]:554 Jim-PC:0 LISTENING</p><p> TCP [::]:2869 Jim-PC:0 LISTENING</p><p> TCP [::]:3306 Jim-PC:0 LISTENING</p><p> TCP [::]:3587 Jim-PC:0 LISTENING</p><p> TCP [::]:5357 Jim-PC:0 LISTENING</p><p> TCP [::]:10243 Jim-PC:0 LISTENING</p><p> TCP [::]:49152 Jim-PC:0 LISTENING</p><p> TCP [::]:49153 Jim-PC:0 LISTENING</p><p> TCP [::]:49154 Jim-PC:0 LISTENING</p><p> TCP [::]:49155 Jim-PC:0 LISTENING</p><p> TCP [::]:49188 Jim-PC:0 LISTENING</p><p> TCP [::]:56756 Jim-PC:0 LISTENING</p><p> TCP [::1]:2869 Jim-PC:50912 ESTABLISHED</p><p> TCP [::1]:50912 Jim-PC:icslap ESTABLISHED</p><p> UDP 0.0.0.0:427 *:*</p><p> UDP 0.0.0.0:500 *:*</p><p> UDP 0.0.0.0:3544 *:*</p><p> UDP 0.0.0.0:3702 *:*</p><p> UDP 0.0.0.0:3702 *:*</p><p> UDP 0.0.0.0:3702 *:*</p><p> UDP 0.0.0.0:3702 *:*</p><p> UDP 0.0.0.0:3702 *:*</p><p> UDP 0.0.0.0:3702 *:*</p><p> UDP 0.0.0.0:4500 *:*</p><p> UDP 0.0.0.0:5004 *:*</p><p> UDP 0.0.0.0:5005 *:*</p><p> UDP 0.0.0.0:5355 *:*</p><p> UDP 0.0.0.0:49985 *:*</p><p> UDP 0.0.0.0:54579 *:*</p><p> UDP 0.0.0.0:56756 *:*</p><p> UDP 0.0.0.0:56757 *:*</p><p> UDP 0.0.0.0:62145 *:*</p><p> UDP 0.0.0.0:62201 *:*</p><p> UDP 127.0.0.1:1900 *:*</p><p> UDP 127.0.0.1:63066 *:*</p><p> UDP 127.0.0.1:63942 *:*</p><p> UDP 127.0.0.1:63943 *:*</p><p> UDP 192.168.1.2:137 *:*</p><p> UDP 192.168.1.2:138 *:*</p><p> UDP 192.168.1.2:427 *:*</p><p> UDP 192.168.1.2:1900 *:*</p><p> UDP 192.168.1.2:50223 *:*</p><p> UDP 192.168.1.2:63065 *:*</p><p> UDP [::]:500 *:*</p><p> UDP [::]:3540 *:*</p><p> UDP [::]:3702 *:*</p><p> UDP [::]:3702 *:*</p><p> UDP [::]:3702 *:*</p><p> UDP [::]:3702 *:*</p><p> UDP [::]:3702 *:*</p><p> UDP [::]:3702 *:*</p><p> UDP [::]:4500 *:*</p><p> UDP [::]:5004 *:*</p><p> UDP [::]:5005 *:*</p><p> UDP [::]:5355 *:*</p><p> UDP [::]:49986 *:*</p><p> UDP [::]:54580 *:*</p><p> UDP [::]:62146 *:*</p><p> UDP [::]:62202 *:*</p><p> UDP [::1]:1900 *:*</p><p> UDP [::1]:63064 *:*</p><p> UDP [fe80::4594:7cd3:b8d5:104e%36]:546 *:*</p><p> UDP [fe80::4594:7cd3:b8d5:104e%36]:1900 *:*</p><p> UDP [fe80::4594:7cd3:b8d5:104e%36]:63063 *:*[/code]</p><p>[/SPOILER]</p><p></p><p>Here is the output of the ping of the server that doesn't work for scheduled direct. It does reach the server. Therefore there must be something either running on the system that causes the conflict or possibly something in the install of my media portal. I am not sure what sort of information media portal puts in the registry that may be causing conflict. I have also gone through numerous reboots and follow the principle of when in doubt reboot.</p><p></p><p>[code]C:\Windows\system32>ping webservices.schedulesdirect.tmsdatadirect.com</p><p></p><p>Pinging docs.tms.tribune.com [54.85.117.227] with 32 bytes of data:</p><p>Reply from 54.85.117.227: bytes=32 time=34ms TTL=52</p><p>Reply from 54.85.117.227: bytes=32 time=31ms TTL=52</p><p>Reply from 54.85.117.227: bytes=32 time=39ms TTL=52</p><p>Reply from 54.85.117.227: bytes=32 time=34ms TTL=52</p><p></p><p>Ping statistics for 54.85.117.227:</p><p> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),</p><p>Approximate round trip times in milli-seconds:</p><p> Minimum = 31ms, Maximum = 39ms, Average = 34ms</p><p>[/code]</p></blockquote><p></p>
[QUOTE="Paul Jackson, post: 1136804, member: 152549"] I found the tvservice error log reported the following. I think it ma be my problem. The scheduler direct works on a system that has no tuners, attatched to the same network. It does not have this error. Both servers are running the same WIN 7 64 bit. The one that is working is a slower sever (much slower) and basically a near fresh install of windows. [SPOILER="Log File"] [code][2015-05-18 08:29:38,335] [Log ] [4 ] [ERROR] - Exception :System.Runtime.Remoting.RemotingException: Remoting configuration failed with the exception 'System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) at System.Net.Sockets.TcpListener.Start(Int32 backlog) at System.Runtime.Remoting.Channels.ExclusiveTcpListener.Start(Boolean exclusiveAddressUse) at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.StartListening(Object data) at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.SetupChannel() at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel..ctor(IDictionary properties, IServerChannelSinkProvider sinkProvider, IAuthorizeRemotingConnection authorizeCallback) at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel..ctor(IDictionary properties, IServerChannelSinkProvider sinkProvider) --- End of inner exception stack trace --- at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark) at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes) at System.Runtime.Remoting.RemotingConfigHandler.CreateChannelFromConfigEntry(ChannelEntry entry) at System.Runtime.Remoting.RemotingConfigHandler.ConfigureChannels(RemotingXmlConfigFileData configData, Boolean ensureSecurity) at System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData configData, Boolean ensureSecurity)'. at System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData configData, Boolean ensureSecurity) at System.Runtime.Remoting.RemotingConfigHandler.DoConfiguration(String filename, Boolean ensureSecurity) at System.Runtime.Remoting.RemotingConfiguration.Configure(String filename, Boolean ensureSecurity) at TvService.TvServiceThread..ctor() [/code] [/SPOILER] I would rather avoid doing a full fresh install on the server that doesn't work. There must be some sort of conflict somewhere. Any pointers and helping to figure out where the conflict is would be helpful. I have tried to uninstall completely media portal and make sure all remaining files have been removed. I'm not sure if anything lingers in the registry. here is an netstat -a without the TV service running [SPOILER="netstat output"] [code]Active Connections Proto Local Address Foreign Address State TCP 0.0.0.0:135 Jim-PC:0 LISTENING TCP 0.0.0.0:445 Jim-PC:0 LISTENING TCP 0.0.0.0:554 Jim-PC:0 LISTENING TCP 0.0.0.0:2869 Jim-PC:0 LISTENING TCP 0.0.0.0:3306 Jim-PC:0 LISTENING TCP 0.0.0.0:5357 Jim-PC:0 LISTENING TCP 0.0.0.0:10243 Jim-PC:0 LISTENING TCP 0.0.0.0:49152 Jim-PC:0 LISTENING TCP 0.0.0.0:49153 Jim-PC:0 LISTENING TCP 0.0.0.0:49154 Jim-PC:0 LISTENING TCP 0.0.0.0:49155 Jim-PC:0 LISTENING TCP 0.0.0.0:49188 Jim-PC:0 LISTENING TCP 0.0.0.0:50851 Jim-PC:0 LISTENING TCP 0.0.0.0:56756 Jim-PC:0 LISTENING TCP 127.0.0.1:1994 Jim-PC:0 LISTENING TCP 127.0.0.1:2869 Jim-PC:50791 TIME_WAIT TCP 127.0.0.1:2869 Jim-PC:50798 TIME_WAIT TCP 127.0.0.1:2869 Jim-PC:50802 TIME_WAIT TCP 127.0.0.1:2869 Jim-PC:50808 TIME_WAIT TCP 127.0.0.1:2869 Jim-PC:50812 TIME_WAIT TCP 127.0.0.1:2869 Jim-PC:50815 TIME_WAIT TCP 127.0.0.1:2869 Jim-PC:50833 TIME_WAIT TCP 127.0.0.1:2869 Jim-PC:50834 ESTABLISHED TCP 127.0.0.1:2869 Jim-PC:50855 TIME_WAIT TCP 127.0.0.1:2869 Jim-PC:50860 TIME_WAIT TCP 127.0.0.1:2869 Jim-PC:50866 TIME_WAIT TCP 127.0.0.1:2869 Jim-PC:50871 TIME_WAIT TCP 127.0.0.1:2869 Jim-PC:50875 TIME_WAIT TCP 127.0.0.1:5357 Jim-PC:50793 TIME_WAIT TCP 127.0.0.1:5357 Jim-PC:50794 TIME_WAIT TCP 127.0.0.1:5357 Jim-PC:50822 TIME_WAIT TCP 127.0.0.1:5357 Jim-PC:50846 TIME_WAIT TCP 127.0.0.1:5357 Jim-PC:50847 TIME_WAIT TCP 127.0.0.1:5357 Jim-PC:50849 TIME_WAIT TCP 127.0.0.1:5357 Jim-PC:50869 TIME_WAIT TCP 127.0.0.1:27015 Jim-PC:0 LISTENING TCP 127.0.0.1:50834 Jim-PC:icslap ESTABLISHED TCP 127.0.0.1:59243 Jim-PC:0 LISTENING TCP 192.168.1.2:139 Jim-PC:0 LISTENING TCP 192.168.1.2:2869 192.168.1.1:50313 TIME_WAIT TCP 192.168.1.2:2869 192.168.1.1:50316 TIME_WAIT TCP 192.168.1.2:2869 192.168.1.1:50319 TIME_WAIT TCP 192.168.1.2:2869 192.168.1.1:50322 TIME_WAIT TCP 192.168.1.2:2869 192.168.1.1:50325 TIME_WAIT TCP 192.168.1.2:2869 192.168.1.1:50328 TIME_WAIT TCP 192.168.1.2:2869 192.168.1.1:50331 TIME_WAIT TCP 192.168.1.2:2869 192.168.1.1:50334 TIME_WAIT TCP 192.168.1.2:2869 192.168.1.1:50337 TIME_WAIT TCP 192.168.1.2:2869 192.168.1.1:50340 TIME_WAIT TCP 192.168.1.2:2869 192.168.1.1:50343 TIME_WAIT TCP 192.168.1.2:2869 192.168.1.1:50346 TIME_WAIT TCP 192.168.1.2:2869 192.168.1.1:50349 TIME_WAIT TCP 192.168.1.2:2869 192.168.1.1:50352 TIME_WAIT TCP 192.168.1.2:2869 192.168.1.1:50355 TIME_WAIT TCP 192.168.1.2:2869 192.168.1.1:50358 TIME_WAIT TCP 192.168.1.2:2869 192.168.1.1:50361 TIME_WAIT TCP 192.168.1.2:2869 192.168.1.1:50364 TIME_WAIT TCP 192.168.1.2:2869 192.168.1.1:50367 TIME_WAIT TCP 192.168.1.2:2869 192.168.1.1:50370 TIME_WAIT TCP 192.168.1.2:2869 192.168.1.1:50373 TIME_WAIT TCP 192.168.1.2:2869 192.168.1.1:50374 TIME_WAIT TCP 192.168.1.2:2869 192.168.1.1:50376 TIME_WAIT TCP 192.168.1.2:5357 192:49381 TIME_WAIT TCP 192.168.1.2:50765 Jim-PC:50763 TIME_WAIT TCP 192.168.1.2:50780 Jim-PC:50773 TIME_WAIT TCP 192.168.1.2:50783 a173-223-204-9:http TIME_WAIT TCP 192.168.1.2:50785 a23-56-83-243:http TIME_WAIT TCP 192.168.1.2:50788 Jim-PC:50781 TIME_WAIT TCP 192.168.1.2:50818 Jim-PC:50781 TIME_WAIT TCP 192.168.1.2:50819 192.168.1.1:5431 TIME_WAIT TCP 192.168.1.2:50823 a23-209-33-144:http TIME_WAIT TCP 192.168.1.2:50824 Jim-PC:50820 TIME_WAIT TCP 192.168.1.2:50827 a23-67-242-65:http TIME_WAIT TCP 192.168.1.2:50828 Jim-PC:50825 TIME_WAIT TCP 192.168.1.2:50829 a23-209-33-144:http TIME_WAIT TCP 192.168.1.2:50830 a23-67-242-65:http TIME_WAIT TCP 192.168.1.2:50838 192.168.1.1:1780 TIME_WAIT TCP 192.168.1.2:50839 192.168.1.1:1780 TIME_WAIT TCP 192.168.1.2:50850 Jim-PC:50842 TIME_WAIT TCP 192.168.1.2:50856 Jim-PC:50851 TIME_WAIT TCP 192.168.1.2:50857 a23-56-83-243:http ESTABLISHED TCP 192.168.1.2:50858 a23-67-244-72:http ESTABLISHED TCP 192.168.1.2:50863 192.168.1.1:5431 TIME_WAIT TCP 192.168.1.2:50867 192.168.1.1:5431 TIME_WAIT TCP 192.168.1.2:50868 192.168.1.1:5431 TIME_WAIT TCP [::]:135 Jim-PC:0 LISTENING TCP [::]:445 Jim-PC:0 LISTENING TCP [::]:554 Jim-PC:0 LISTENING TCP [::]:2869 Jim-PC:0 LISTENING TCP [::]:3306 Jim-PC:0 LISTENING TCP [::]:3587 Jim-PC:0 LISTENING TCP [::]:5357 Jim-PC:0 LISTENING TCP [::]:10243 Jim-PC:0 LISTENING TCP [::]:49152 Jim-PC:0 LISTENING TCP [::]:49153 Jim-PC:0 LISTENING TCP [::]:49154 Jim-PC:0 LISTENING TCP [::]:49155 Jim-PC:0 LISTENING TCP [::]:49188 Jim-PC:0 LISTENING TCP [::]:56756 Jim-PC:0 LISTENING TCP [::1]:2869 Jim-PC:50912 ESTABLISHED TCP [::1]:50912 Jim-PC:icslap ESTABLISHED UDP 0.0.0.0:427 *:* UDP 0.0.0.0:500 *:* UDP 0.0.0.0:3544 *:* UDP 0.0.0.0:3702 *:* UDP 0.0.0.0:3702 *:* UDP 0.0.0.0:3702 *:* UDP 0.0.0.0:3702 *:* UDP 0.0.0.0:3702 *:* UDP 0.0.0.0:3702 *:* UDP 0.0.0.0:4500 *:* UDP 0.0.0.0:5004 *:* UDP 0.0.0.0:5005 *:* UDP 0.0.0.0:5355 *:* UDP 0.0.0.0:49985 *:* UDP 0.0.0.0:54579 *:* UDP 0.0.0.0:56756 *:* UDP 0.0.0.0:56757 *:* UDP 0.0.0.0:62145 *:* UDP 0.0.0.0:62201 *:* UDP 127.0.0.1:1900 *:* UDP 127.0.0.1:63066 *:* UDP 127.0.0.1:63942 *:* UDP 127.0.0.1:63943 *:* UDP 192.168.1.2:137 *:* UDP 192.168.1.2:138 *:* UDP 192.168.1.2:427 *:* UDP 192.168.1.2:1900 *:* UDP 192.168.1.2:50223 *:* UDP 192.168.1.2:63065 *:* UDP [::]:500 *:* UDP [::]:3540 *:* UDP [::]:3702 *:* UDP [::]:3702 *:* UDP [::]:3702 *:* UDP [::]:3702 *:* UDP [::]:3702 *:* UDP [::]:3702 *:* UDP [::]:4500 *:* UDP [::]:5004 *:* UDP [::]:5005 *:* UDP [::]:5355 *:* UDP [::]:49986 *:* UDP [::]:54580 *:* UDP [::]:62146 *:* UDP [::]:62202 *:* UDP [::1]:1900 *:* UDP [::1]:63064 *:* UDP [fe80::4594:7cd3:b8d5:104e%36]:546 *:* UDP [fe80::4594:7cd3:b8d5:104e%36]:1900 *:* UDP [fe80::4594:7cd3:b8d5:104e%36]:63063 *:*[/code] [/SPOILER] Here is the output of the ping of the server that doesn't work for scheduled direct. It does reach the server. Therefore there must be something either running on the system that causes the conflict or possibly something in the install of my media portal. I am not sure what sort of information media portal puts in the registry that may be causing conflict. I have also gone through numerous reboots and follow the principle of when in doubt reboot. [code]C:\Windows\system32>ping webservices.schedulesdirect.tmsdatadirect.com Pinging docs.tms.tribune.com [54.85.117.227] with 32 bytes of data: Reply from 54.85.117.227: bytes=32 time=34ms TTL=52 Reply from 54.85.117.227: bytes=32 time=31ms TTL=52 Reply from 54.85.117.227: bytes=32 time=39ms TTL=52 Reply from 54.85.117.227: bytes=32 time=34ms TTL=52 Ping statistics for 54.85.117.227: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 31ms, Maximum = 39ms, Average = 34ms [/code] [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
Schedules Direct US/Canadian/Mexico EPG Plugin (Updated August 2010)
Contact us
RSS
Top
Bottom