MVP Networking issue

[johnvk]

Wired network is used only to connect to the MVP.
Wireless network is used to connect to the Internet.

Windows IP Configuration
Host Name . . . . . . . . . . . . : woonkamer
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : LDU9

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Generic Marvell Yukon Chipset based Gigabit Ethernet Controller
Physical Address. . . . . . . . . : 00-30-1B-B5-78-DB
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 169.254.4.149
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Ethernet adapter Wireless Network Connection:
Connection-specific DNS Suffix . : LDU9
Description . . . . . . . . . . . : NETGEAR WG121 802.11g Wireless USB2.0 Adapter #2
Physical Address. . . . . . . . . : 00-09-5B-5F-0B-0A
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
Lease Obtained. . . . . . . . . . : woensdag 6 juli 2005 22:28:28
Lease Expires . . . . . . . . . . : dinsdag 19 januari 2038 5:14:07
[/FONT]

[LilY0da]

From your wired LAN config:

Code:

IP Address. . . . . . . . . . . . : 169.254.4.149

That means that you have no real IP address on your wired LAN. It's called an APIPA IP address.
A 169.254.X.X IP means that you have set your interface to get an IP from a DHCP server, and no DHCP server has responded (which is normal if the only thing on that segment is your PC and the MVP).
http://expertanswercenter.techtarget.com...48,00.html

To be honest, I'm not even sure why it's working when the wireless LAN is down... I guess cause your PC has no better path to send packets to than the gimped wired interface

IMHO you need to specify an IP on your wired LAN interface config. I recall seeing the IP to put in to make it work with the MVP in the paper doc that came with it, in a section about connecting the MVP directly to a laptop or something... I think it's 192.168.0.1 with a netmask of 255.255.255.0, but you should check the docs first.

[johnvk]

Thanx for thing along. On the 169.x segment there isn't a DHCP-server. The IP-number is hardcoded (by me). I'll give it a try changing to 192.168.x and see if the MVP picks it up.

My best guess is that GBPVR send packets to the first network found (according to the logs 192.x) or the the network with a DHCP-server, but the MVP is on the other network.

John

[LilY0da]

I just saw that the manual is available in PDF on Hauppauge website
http://hauppauge.lightpath.net/manuals/m-mediamvp.pdf

The IP is apparently 192.123.1.1/24

Quote from page 18 - Step4 is the one you should do

1. Purchase or make a cross over Ethernet cable. Examples of a crossover cable are the Belkin CAT 5e Crossover Cable for computer-to-computer connection
2. Connect one end of the crossover cable to the LAN port on the MediaMVP, and the other end to the LAN port on your PC or laptop
3. Make sure the MediaMVP software is installed on your PC. See “Installing the MediaMVP software” section.
The next step is optional. If you do not perform step 4, it will take about 3 minutes to make a connection between the MediaMVP and your PC
4. Set a fixed IP address on your PC when using a crossover cable.
When using a direct connection with a network crossover cable, you need to set a static IP address on your PC.
To do this, click Start / Settings / Control Panel / Network connections. Double click on Local Area Connection and then click Properties. Click on Internet Protocol(TCP/IP).
Double click Advanced and you will see the Internet Protocal (TCP/IP) Properties menu.
Uncheck Obtain an IP address automatically.
In the IP address box, enter 192, then 123, then 1, then 1.
When you hit the Tab key, the subnet mask will fill in to 255.255.255.0
Click OK and then OK again to complete the disabling of DHCP.
If you would like to reenable DHCP, simply click the Obtain an IP address automatically box, and your system will be configured for use on a network instead of the direct PC to MediaMVP connection.
5. Connect the MediaMVP to the TV set, and turn on the MediaMVP. You should see the 'Searching for PC server' on the TV set. On the PC, you should see a Windows massage say 'Ethernet connection found'

[johnvk]

Thank you very much for the research, but unfortunalitely it doesn't work.

7-7-2005 22:56:53.703 INFO [77] ServiceLocatorThread() Hostname: woonkamer
7-7-2005 22:56:53.734 INFO [76] MVP Streaming thread starting
7-7-2005 22:56:53.734 INFO [76] MVP Streaming thread Listening on port: 8337
7-7-2005 22:56:53.734 INFO [75] MVP Control thread Listening on port: 5906
7-7-2005 22:56:53.750 INFO [77] IP Address 192.168.2.4
7-7-2005 22:56:53.750 INFO [77] IP Address 192.123.1.1
7-7-2005 22:56:53.750 INFO [79] BOOTPWorkerThread() Hostname: woonkamer
7-7-2005 22:56:53.750 INFO [79] BOOTPWorkerThread IP Address 192.168.2.4
7-7-2005 22:56:53.750 INFO [79] BOOTPWorkerThread IP Address 192.123.1.1
7-7-2005 22:56:54.265 VERBOSE [76] MVP Streaming thread waiting for connection
7-7-2005 22:56:54.265 VERBOSE [75] MVP Control thread waiting connection
7-7-2005 22:56:58.812 VERBOSE [77] Received MVP Service Locator request
7-7-2005 22:56:58.812 VERBOSE [77] Parsing MVP Service Locator request
7-7-2005 22:56:58.812 VERBOSE [77] About construct MVP Service Locator request
7-7-2005 22:56:58.812 VERBOSE [77] Sending MVP Service Locator response to 100FEA9:16882
7-7-2005 22:57:06.796 VERBOSE [77] Received MVP Service Locator request
7-7-2005 22:57:06.796 VERBOSE [77] Parsing MVP Service Locator request
7-7-2005 22:57:06.796 VERBOSE [77] About construct MVP Service Locator request
7-7-2005 22:57:06.796 VERBOSE [77] Sending MVP Service Locator response to 100FEA9:16882
7-7-2005 22:57:14.796 VERBOSE [77] Received MVP Service Locator request
7-7-2005 22:57:14.796 VERBOSE [77] Parsing MVP Service Locator request
7-7-2005 22:57:14.796 VERBOSE [77] About construct MVP Service Locator request
7-7-2005 22:57:14.796 VERBOSE [77] Sending MVP Service Locator response to 100FEA9:16882

Only thing that works is disabling the wireless network and restarting the GBPVR recording service....

Also installed a fresh OS with only GBPVR. Don't know how, but in that case the 169 (wired) network is in the GBPVR-logs mentioned before the 192 (wireless) network and all works fine.

Guess I'll adjust restart.bat where the wireless network is disabled before the GBPVR service is started.....

John

[Lucas_24]

I havn't tried this yet, just upgraded my setup and I now have 2 network cards. Under windows, you're able to share a connection. Which means one card is connected to the internet, now all PC's on the other card can share the connection. Now this is not what we're trying to achieve here, but a by product of this is that the second connection "the one not connected to the internet" now has a DHCP service running on the dual homed box. So windows will now assign an IP address to the MVP. So your not really sharing the internet, but you've just created a DHCP server on your MVP network. I'll be testing this this weekend if it rains. If you don't know how to set it up just search for ICS or Internet connection sharing on Google.

[LilY0da]

Beats me... To me your log shows GBPVR working, it's responding to the MVP...
It could be responding with the wrong IP address though.

Did you have your wireless connection installed in your PC before or after the wired one?
Try to delete the oldest connection, and recreate it. It may switch the order in which GBPVR detects the LANs.
If that doesn't work, try changing the connection names around. Maybe GBPVR takes them in alphabetical order.

I think we need a dev input on how the thingy works...

[johnvk]

Hi All,

Finally i've got it nailed down
As long as I leave the Hauppauge MVP srv service running (not the GUI-service), all works fine. Apparently this service grants an IP-number to my mediaMVP from where GBPVR takes it further. Works even with the wireless network on.

Thanks for thinking along

[MediaDogg]

Hi I just saw this thread. Looking at your log, your DHCP server is at 192.168.2.1. So it will not repsond to requests or assign addresses in the 192.168.1.x range - that is probably why the MVP is not being recognized.

Did you try setting your wired LAN to 192.168.1.x instead of 192.168.2.x ? I think it will work then. I had a similar problem back when I first set up my MVP.

My apologies in advance if I misunderstood your situation.