97.9 update does not connect to server

[marcomessina]

I have run with versions prior to 97.9 for many months with no trouble. Since upgrade I've not been able to playback on MVP

I use direct connect between PC and MVP as specified by Hauppauge (ip 192.123.1.1 on PC) and it worked for months prior to upgrade to 97.9.
GBPVR on console works OK

I presume MVP IP is 192.123.1.2 because it responds to ping from the PC and there are no other devices on the cable

Config program seems to work OK

Tray seems to load and behave OK

Recording service loads and works OK

Playback on MVP using Hauppauge swr works ok

Hauppauge swr when loaded manually connect MVP with no problems.

GBPVR is configured to autostart one server (as it was in the past)

Even starting a server manually does not help (it used to in the prior versions)

If left on "cannot connect to server" long enough, eventually a screen appears that shows available servers saying that no server can be found; additional scans for servers do not help (MVP native software connects, however and after it is stopped GBPVR still cannot find server). Scan is the only option available and does nothing.

Any suggestions would be welcome.
[ATTACHMENT NOT FOUND]

[HtV]

Did you stop both hauppauge mvp services.
Edit: did you read this thread: http://forums.nextpvr.com/showthread.php?t=16286&page=6

[marcomessina]

HtV, thanks

Did you stop both hauppauge mvp services

Yes I did. MVP software does not load unless explicitly started, and I verified that services are not started (although configured for autostart but not running when I run GBPVR). I also explicitly stopped the MVP swr repeatedly using the MVP provided script.

Edit: did you read this thread: http://forums.nextpvr.com/showthread.php?t=16286&page=6

I did now and felt very inadequate regarding my certifications :o

Most seemed to deal with routers and DHCP. I use direct connect and fixed IP, so I do not see how it relates.

References to dongle make me point out that I am using dongle-3.0.24088.bin that came with GBPVR, but the plain dongle.bin (also with gbpvr) behaved the same way. Between those two is one preferred while I tryt o debug my issues?

[HtV]

from the logs:

Code:

6/13/2006 11:06:29 PM.578 INFO [5] ServiceLocatorThread() Hostname:  tivo
6/13/2006 11:06:29 PM.578 INFO [7] BOOTPWorkerThread() Hostname:  tivo
6/13/2006 11:06:29 PM.578 INFO [5] IP Address 192.168.0.4
6/13/2006 11:06:29 PM.578 INFO [5] IP Address 192.123.1.1
6/13/2006 11:06:29 PM.578 INFO [7] BOOTPWorkerThread IP Address 192.168.0.4
6/13/2006 11:06:29 PM.578 INFO [7] BOOTPWorkerThread IP Address 192.123.1.1
6/13/2006 11:06:29 PM.593 INFO [9] MVP Streaming thread Listening on port: 8337
6/13/2006 11:06:29 PM.593 VERBOSE [9] MVP Service Locator will resolve media port: 8337
6/13/2006 11:06:29 PM.593 VERBOSE [9] MVP Streaming thread waiting for connection

Any idea where the ip 192.168.0.4 comes from, maybe your usb wifi.
maybe try with the wifi disconnected.

[marcomessina]

Yes that IP is the USB WIFI. It always worked fine and I need it to pull the program schedule from zap2it

[HtV]

I'm thinking it's maybe getting mixed up, in my logs there's always only one bootworker thread ip, that's the ip from my computer.

[ram4x4nut]

Most seemed to deal with routers and DHCP. I use direct connect and fixed IP, so I do not see how it relates.

It relates because this problem has absolutely nothing to do with routers or dhcp. No other version behaved this badly, so it must be something in 97.x that is not firing properly. Some people have had luck putting up software dhcp servers in place of good hardware (in most cases hardware running a small LINUX OS) which in my opinion is fixing the symptom not fixing the problem.

[onestar]

Some people have had luck putting up software dhcp servers in place of good hardware (in most cases hardware running a small LINUX OS) which in my opinion is fixing the symptom not fixing the problem.

But come on does it matter? As long as it works? I now have 100% reliable switch on and off. And in my opinion its not the DHCP thats the problem or solution.

Its the TFTP server, with the DHCP providing the necessary option flags to direct it to the TFTP server.

As far as I could see the MVP and GBPVR did communicate upto the point of sending the dongle, and lost it thereafter. But with a dedicated TFTP its carries on through to the next stage, which then works fine.

[ram4x4nut]

Come on, what's wrong with using Windows Server 2003 SE as your Router on any PC you have that you're not using. As long as you can put two NIC cards in there. 1-LAN and 1-WAN with DHCP Server it works better than the cheap routers with poor network packet management.

First off, why use an entire a PC when a GOOD router is not only cheaper to purchase, but to maintain and power, not to mention the cost of a Server 2003 SE license. Personally I run as little MicoSoft crap as possible because of the hundreds of security problems they have.

Second, I question the validity of your "poor network packet management" statement. Where's the proof? I ask that for most other people because I do not run the stock router software (Linux utilizing IPChains and IPTables) on my WRT54G. I run DD-WRT (a custom-created Linux os with many additional features beyond that of the stock OS) which I have customized even more for my own use (including the use of QoS which Server 2003 ES tries to do but doesn't do it well). Even at that ... anybody who has done a little research knows that the Linksys routers are actually powered by the Broadcom processor and Cicso Linux build for the OS which is as good as you will find for home use, and in my opinion much better than the klunky and security hole laden MS Server 2003 ES.

But if Server 2003 ES works for you that's great. I just don't see it as a feasable and reasonable solution for most home users who don't have a spare PC and a couple hundred $$US to plunk down on yet another problematic MicroSoft product.

If routers/dhcp/tftp were the base problem, this would have been a much bigger issue in GBPVR releases prior to 97.x As I said before, all of these little fixes are, in my opinion, addressing the symptom, not the cause, of the problem.

Not connecting to the DHCP Server should tell you something is wrong with the Router. Ping trace, scan your Router and Network PCs you can use LAN Spy to see what's going on.

I never once said my MVP wasn't talking to the DHCP server. It in fact is. It get's it's IP, it loads the dongle (HINT tftp is working just fine) but when it tries to talk to the application it fails.
Likewise,the many virtual machines I use in VMWare never have a problem with acquiring an address, or maintaining a network connection. And yes they are using bridged networks so they get their very own MAC and IP addresses.


Just my $0.02

[zehd]

Come on, what's wrong with using Windows Server 2003 SE as your Router on any PC you have that you're not using.

marcomessina is using one cable, (crossover) to connect his MVP. That implies he does not have 'another' computer he's not using.

Windows 2003 Server costs money. Surely your're not suggesting pirating...

As long as you can put two NIC cards in there. 1-LAN and 1-WAN with DHCP Server it works better than the cheap routers with poor network packet management.

Yes, a Windows server may route better, but at what expense? It's not nearly as easy as buying a 50-100 dolar router and using 'your' network tweaks...