pvrx2 phoning home?

[K.S.]

@anyone regarding the talk-home part: if you have XP installed and only the out of the box SP2 firewall installed, check out the firewall log, might have some additional info... C:\WINDOWS\pfirewall.log

Just Googled Welltonway... http://www.welltonway.com/english/

old news :-)
because of the "crashed" homepage you can't access the news posted there, but sub made it official that the core of gbpvr is also used by wellton way in their own media center solution...

[InVermont]

I reset the firewall and it came up again but with no specific destination.
CV

If memory serves, the Windows Firewall (on XP) is one way. Outbound connections are not checked or blocked. If it were 'calling home', you wouldn't get any notice.
So what you are seeing is PVRX2 opening up a port to receive connections, which is to be expected if it and the recording service exchange data via IP.

Even if you have cleared PVRX2 before, the change of build number should invoke the firewall again.

[sub]

If memory serves, the Windows Firewall (on XP) is one way. Outbound connections are not checked or blocked. If it were 'calling home', you wouldn't get any notice.
So what you are seeing is PVRX2 opening up a port to receive connections, which is to be expected if it and the recording service exchange data via IP.

Even if you have cleared PVRX2 before, the change of build number should invoke the firewall again.

Yes, I think your logic is right.

[SFX Group]

I have just noticed this (the moment the tray icon needs to change first time to show its doing something) you get the FIREWALL unblock...

Looks like the reason is this in the config.xml...

<RecordingServiceLocation>tcp://127.0.0.1:7968/RecordingRemote</RecordingServiceLocation>

[martint123]

If you actually read the bottom of the firewall message in post 3 it says it is warning about accepting connections - nothing at all about wanting to send anything.

[Fatman_do]

I have just noticed this (the moment the tray icon needs to change first time to show its doing something) you get the FIREWALL unblock...

Looks like the reason is this in the config.xml...

<RecordingServiceLocation>tcp://127.0.0.1:7968/RecordingRemote</RecordingServiceLocation>

That is the Local Host (aka your machine) talking to itself.

[SFX Group]

127.0.0.1 is always (and only) the local machine, interesting how Microsoft are firewalling its own local address....

If something is going to talk to an IP address then something must be there to "accept" or "listen" so it stands to reason if theres a talker then there will be a listener as well the other end (assuming everything works), so the Firewall will do this.

In this case "otherend" and "talker" are the same machine, just a method to talk to each other, i know why this was done so the server client idea works.