version 2.0.0.400 seems to have broke remote connection

[sspell]

wow! 387 had remote drive pool UI connection working great now with the 400 update no more remote control. I have all the peers set the same as in 387 in remote.default set exceptions for the program in firewall opened inbound and outbound ports TCP 27515 on server and client no luck. Any help appreciated. client win8 server whs2011. By the way it works fine in the server connector as a plugin but to me that is a slower process than the drive pool remote UI.

[Christopher (Drashna)]

Just want to make sure, all the clients are using build 400 as well, right?

 

And you've double checked that the peer list is still properly configured.

[sspell]

yes and yes but I'll double check everything

[sspell]

Well I found the issue with the remote drive pool. The firewall settings was blocking it so now fixed and it's working great sorry for not checking this problem out sooner.

[Christopher (Drashna)]

The firewall would definitely do that. But that should have been configured properly when you installed DrivePool. Unless you're using a 3rd party firewall.

[sspell]

Yea I'm using Symantec smb endpoint protection probably why it didn't configure go figure...lol

[x-ares-x]

Hello,

 

remote control is not working here.

Installed it on my server and allowed remote control.

Just using MS Firewall, Rules are added automatically.

Should have nothing to do with my router, hm?

It's not blocking in LAN.

 

Added the Pools with IPs in the RemoteControl.xml,

changed nothing.

 

Disabled Firewall on Server for a test..

changed nothing either...

 

Can you help me?

 

Using WHS2011 Server and Win8 Client.

 

Edit:

Disabled: Client FW, Server FW and Sophos on-access Scan...

 

My Router is a fritzbox... the server is found as "homeserver.fritz.box"... this is ok?

Edited September 16, 2013 by x-ares-x

[sspell]

have you set the peers in remote.default and opened port TCP 27515 in firewall. by the way mine was working now suddenly stopped again. I think my firewall is blocking it again for some reason.. I'll have to check it out kind of frustrating smb endpoint firewall that is..

[Christopher (Drashna)]

@x-ares-x:

Yes, that is fine. you're router is adding it's name as a "dns suffix", and that may be normal for it.

But yes, make sure you add the TCP port "27515" to the allowed list for your firewall, on the client. That or...

 make sure that the DrivePool.Service.exe file is added to the list of exceptions on both machines.

 

 

@sspell: I used to use Symantic for firewall... till I discovered it's a bit overzealous, as you're noting. 

Make sure you add said port the the "allow" list, as a network Service, If you haven't already.

[x-ares-x]

@x-ares-x:

Yes, that is fine. you're router is adding it's name as a "dns suffix", and that may be normal for it.

But yes, make sure you add the TCP port "27515" to the allowed list for your firewall, on the client. That or...

 make sure that the DrivePool.Service.exe file is added to the list of exceptions on both machines.

 

The Windows Firewall was disabled on both systems, shouldn't that be enough for a test?

[sspell]

yea I disabled my firewalls too and no shebang what's funny it started working for a little while back when I was fiddling with the firewall setting. That's what made me think firewall issue but alas that's not the case something else is going on.

[x-ares-x]

Disabling Firewall give no result,

but!

Outgoing Rule in the SErver for the DrivePool.Service.exe..

 

Thanks... working now.. :-)

[Christopher (Drashna)]

I've flagged Alex about this, so he can take a look, and see if he can fix it on our end.

 

But this sounds like a weird issue with Windows Firewall....

[sspell]

Just a word of note. I have not been able to get the remote control working in the 400 version. It only worked briefly for a short period. But I just recently had a update for my NVidia video driver, I have a GeForce gtx 670 card from Asus on the remote client the server has amd video, and the remote control immediately started to work after the required reboot from the driver update. I had checked the remote control before and after the update. Now to me this seems like it could be something in the video area that needs addressing. But for now it is working perfectly again so the video driver fixed the issue for me..

[Christopher (Drashna)]

@sspell, it sounds like maybe an issue with the driver causing issues with other hardware, but I'm not sure.

 

Hopefully, the issue doesn't come back.

 

@x-ares-x: are you still having issues here? 

If so, could you try reinstalling DrivePool?

http://wiki.covecube.com/StableBit_DrivePool_Q3017479

[sspell]

Well darn it 417 broke the remote control connection again just after I got it working in the 400 version. Tried rolling back video driver that did nothing. checked my settings they all transferred with the 417 update so that is good. I am at a loss to figure out what's causing this my firewall is the same as in the 400 version when it was working..

[sspell]

Something fouled up my firewall settings. I deleted all the rules I set for drive pool and redone new rules and it's working in 417 so far.. I set a rule for udp and opened All ports I don't think that is needed so I'll delete that rule. hope it continues to work..

[Alex]

Sspell,

 

I haven't really changed anything at all regarding remote control, in build 400+. It looks like the issue is resolved. Let me know if the problem resurfaces.

[sspell]

Well the saga continues drive pool has been working great remotely. One thing I noticed is after a update with windows it'll knock it out for a while. But remote starts to work again. The latest is I'm trying out the scanner remote in the latest beta release and it worked when I first installed the scanner then after a reboot neither drive pool or scanner remote is working so both are knocked out now. I set the peers on scanner after the reboot and nothing working and opened the firewall port then too. I'll give it a few days to see if it starts to work. I have seen no notices and have the firewall set to notify if it blocks a program. My best guess is windows firewall marks a suspect program and even if you get the settings right it will continue to block it for a while. Only thing I can think of for this type behavior. You gotta love M.S.

[sspell]

All working again. I'm pretty confident there is some temporary blocking going on with the firewall. And it is every time there is a change in the program status or something updated.

[Christopher (Drashna)]

Are you just using Windows Firewall? Any virus scanner on the server? And on the client?

 

That and maybe restart the Windows Firewall service when this happens. Maybe it's just being childish and not letting go of packets... for a lack of a better description.

[sspell]

Yes I'm using Windows Firewall now and Symantec endpoint for virus less the Symantec firewall. I think the problem lies somewhere in windows 8 may be the firewall. I was having similar problems when using the Symantec Firewall. So it's like u said I really don't think it's the server could be the problem though. For what I know...

[Christopher (Drashna)]

Well, unfortunately, I've seen similar issues (not with DrivePool, but with WHS) with a firewall installed. Even with it disabled, it can still cause issues.