[fixed] Client : Connetion to server problem with multiple network interfaces (1 Viewer)

[MJGraf]

The exception regarding movies above seems to have something to do with the LocalFSResourceProvider on the server side. Logs attached from client and server when trying to play a simple avi located on a local harddisk on the server. Don't know whether this has something to do with the http-binding or not...

cheers,
Michael

 

[morpheus_xx]

AW: Client : Connetion to server problem with multiple network interfaces

Please ensure that you have MP2 server re-compiled as well. There were major changes, so do a cleanup of the output folder and compile again.

 

[MJGraf]

Thanks Morpheus,

well, what I did is: delete everything related to MP2 on all my machines. Even deleted MP2-Sourcecode and did a fresh Git-clone. In the master branch, the http-binding is not yet included. The branch mentioned by Albert in his last post wasn't there anymore. But I saw that in the "dev" branch, the http-binding changes were also included. So I took this branch and did a completely fresh build of client and server.

What I tried to do is play a simple avi file located on a local harddisk of the server (i.e. added a global video share)

On the server side, there's no more error in the logs. But the client still can't play the avi, rasing an exception somehow related to the resource access (client logs attached). Furthermore it seems that iso files are no longer shown in the global share (only the one avi and some ts-recordings from MP1-TV-Server are shown).

If this is due to the fact that I'm playing with the dev branch here, please let me know. I'm happy to wait until all these changes are committed into the master branch after they are completed. I just wanted to further test the http-binding, which seems only possible with this dev-branch. Anyway, I can still confirm that http-binding works as it should.

So assuming that the exception is due to some changes not being complete, I'll be quiet now. But if there's anything I can help you guys with (in particular testing...), please let me know.

Michael

 

[Albert]

AW: Client : Connetion to server problem with multiple network interfaces

MJGraf, your problems come from our DOKAN virtual drive handling which blocked a thread at the start of MP2 before it is able to unmount a mounted drive from a former unclean MP2 shutdown. The latest commit in the dev branch should fix that problem. After that, you should be able to go into ISO and ZIP files again.

 

[MJGraf]

Seems like I'm still getting an exception while the importworker tries to analyze my iso files...

 

[Albert]

AW: Client : Connetion to server problem with multiple network interfaces

F.... ISO reader. I hope we get a better implementation some time.

How big is that ISO file? Can you give it to me?

 

[Albert]

AW: Client : Connetion to server problem with multiple network interfaces

Ok, seems that I produced the problem, so it's not the fault of the ISO reader. I just fixed it.

 

[MJGraf]

I think we can close this one after Albert did a great job in coping with my lack of programming knowledge today ;-)
http-binding works correct in the dev-branch.
Michael

 

[Smeulf]

I think we can close this one after Albert did a great job in coping with my lack of programming knowledge today ;-)
http-binding works correct in the dev-branch.
Michael

Sorry, but I disagree : Unfortunately, I still have a problem here.

When I use the server from the Dev branch, Dev branch's client can see the server, but the server always says the client is disconnected.

If I start my patched client with the same server, then the server can see the client, and says it's connected...

Next test : I replaced the Dev branch server with my patched server : exact same result, my patched client works correctly, the Dev branch one doesn't.

So my conclusion it that's there's still something wrong with the client, if I believe my quick tests. I'll investigate again during the week or the week-end, depending of my free time.

My test environnement is still :
- 2 computers, one hosting the server, the other one the client of course
- both computers have 1 physical interface and 2 virtual interfaces

Sorry it still not 100% fixed But we'll win at the end !

Cheers.

Smeulf.

 

[Smeulf]

Well, it's now very difficult for me to reproduce the problem. I had it only once today, at the very first time and could'nt debug it. After that, it was working as expected.

The problem does not to afect the client functionalities, only the server doesn't display the client name and/or status (connected or not).

Maybe it has something to do with my laptop firewall (symantec firewall is so strange sometime...).

I don't know what to do more with this issue, and we have to remeber it's in some specific cases, witch won't be the "normal" configuration. Maybe we should close it and wait... Or set it to "will not be fixed" for now.

Cheers.