Problem with TV Server and WLAN (1 Viewer)

[Shazell]

SOLVED!!

Ok this is what I did

Installed a Loopback Adapter
How to install the Microsoft Loopback adapter in Windows XP

I now have two NIC's the wireless and the Virtual NIC from the loopback adapter

I switched to letting XP control my wireless network instead of the belkin software

I then selected both NIC's in the network interfaces window and created a network bridge
Setting Up Network Bridge in Windows XP

The bridge was initially configured to use DHCP and obtained a new IP from my router. I then assigned it a static IP within the routers range (actually the same as it got from DHCP and changed the router config to allow that.)

Now the tvserver always starts with the IP of the bridge and has no problems if the wireless drops out

I can connect from the desktop PC using https://forum.team-mediaportal.com/mp-tv-client-262/announce-mptvclient-v1-2-5-20-12-2007-ii-22027/ mediaportal itself on the desktop did not work first go but I think thats not a related problem.

But me is VERY happy

 

[charli181]

Great to hear and thanks for sharing your results....

 

[Shazell]

I have discovered that there is a bit of a side effect with my solution that means having the router switched off causes stuttering

This new stuttering was regular, about every 60 seconds. And it was definitely processor related as if I was moving the mouse at the same time the mouse pointer would also freeze. Using Process explorer I could see spikes in CPU usage every 60 seconds with a process called System:4 using almost 100%.

This was due to the wireless network connection trying to connect when my router was switched off. With the router switched on the WLAN connects and the stutter stops. I am only using a single core CPU atm I expect multicores will not have this issue.

Anyone encountering stutters I would suggest using Process Explorer and looking at CPU usage graphs to see if there are any other issues.

The problem is not caused by Mediaportal, but I am not sure how to solve it other than leave the router on

 

[Shazell]

I have discovered that there is a bit of a side effect with my solution that means having the router switched off causes stuttering

This new stuttering was regular, about every 60 seconds. And it was definitely processor related as if I was moving the mouse at the same time the mouse pointer would also freeze. Using Process explorer I could see spikes in CPU usage every 60 seconds with a process called System:4 using almost 100%.

This was due to the wireless network connection trying to connect when my router was switched off. With the router switched on the WLAN connects and the stutter stops. I am only using a single core CPU atm I expect multicores will not have this issue.

Anyone encountering stutters I would suggest using Process Explorer and looking at CPU usage graphs to see if there are any other issues.

The problem is not caused by Mediaportal, but I am not sure how to solve it other than leave the router on

I had forgotten to add that I solved the problem with the high CPU usage with no WLAN connection, the solution is to use the manufacturers drivers/software to connect to the wireless and then disable the Windows Wireless Zero Configuration

Turning off Wireless Zero Configuration

It is that service that is causing the high CPU usage, unfortunately my wireless software (Belkin) does not work within a network bridge

https://forum.team-mediaportal.com/plugins-47/mpstandbyhandler-44296/ plugin should sort that problem out though

 

[crazyfool]

sorry to revive an old thread but I am having the problem said here and I cant seem to solve it with a network bridge. I have configured the tvserver to use the ip address 192.168.1.1 which works find for the singleseat... I then have a wireless nic with the ip address 192.168.1.100... i then created a bridge with the ip address 192.168.1.2... however i cant seem to connect to the server from any of the clients... its just doesn't find the server... and mp seems to crash on the clients if i try and enter an ip address instead of a server name... don't suppose anyone has any ideas?

 

[paddy01]

192.168.1.1 is quite possibly the address that your router has for itself, therefore it's entirely possible that you've got 2 devices on the network trying to use the same IP address.

Try and avoid using IP address at he extreme ends of the range.. i.e. avoid 192.168.1.1 and 192.168.1.254