Page 1 of 1

Problems Connecting to CloudPod

PostPosted: Fri Jul 01, 2022 2:53 am
by Lance Lewis
I have my cloudpod working on most of our computers....but I have one windows computer that is connecting. It's a windows 10 (64 bit) and it never asks me for admin and password but instead that it just can't connect and suggest the name is wrong. Can't seem to figure it out. Any thoughts? I know I didn't give much to go by. Our windows 11 computer and windows 10 computer and MAC have all connected no problem.

Re: Problems Connecting to CloudPod

PostPosted: Mon Aug 01, 2022 4:14 pm
by Juergen Engelke
Seems to be the well known USB Cable Problem (same Problem with USB and USB cable on Cameras) !
So try different USB cables.

Re: Problems Connecting to CloudPod

PostPosted: Mon Aug 08, 2022 11:48 pm
by Mark Baird
This is not a USB cable issue. the cloud pod only connects locally over USB. when connecting to workstations over the network it is all Cat 6.

I am having this same problem. Any help with the networking end would be appreciated. It seems the windows network discovery on these units are not at all robust. I have succeeded in mapping them using a static IP address, but windows still looses track of them afternot thirty minutes or so. very very frustrating! and I am having the issue with two windows 10 pro computers and a windows 11 pro machine.

Re: Problems Connecting to CloudPod

PostPosted: Wed Aug 10, 2022 1:12 am
by Lance Lewis
Mark,

I have solved this problem today!!!!

In general, what you have to do is create a new Windows Credential. I will give specific steps below.

Like you I had some computers that would connect, and some that would just tell me that it couldn't connect and I should check the name. It never would ask me to enter user name and password. For whatever reason on two of my five computers (4 PCS and 1 Mac) the option just never came up.

The process is super simple.

1. Go to Control Panel>User Accounts>Credential Manager
2. Select "Windows Credentials"
3. Select "Add a Windows Credential"
4. For the Internet or network address type in The exact name of your cloud pod
5. The type in "guest" for user name and "guest" for password.

Worked for me (literally figured it out today).

It should be noted that if you are on a homegroup that the user name might need to be "workgroup/guest" as stated on page 7 of the manual.

Let me know if this works for you. I was bummed for weeks until I finally figured it out today.

Re: Problems Connecting to CloudPod - SOLVED

PostPosted: Fri Aug 12, 2022 4:27 pm
by JimODB3000
I cannot get any of my windows machines 10 or 11 clients to connect to my Cloud Pod. I've tried the windows credential manager method specified above but that did not work for me. My windows clients are a remember of a domain and I'm wondering if that is part of my issue? I have one mac client that connects without issue.

The error on windows is that "the network path cannot be found"

Everything I've tried has been unsuccessful.

Re: Problems Connecting to CloudPod - SOLVED

PostPosted: Tue Aug 16, 2022 9:11 pm
by Lance Lewis
when you go into windows credential manager did you see clouded already listed? If not, when you added it did you verify the following:
1. the spelling of the name is exactly the same
2. the user name is "guest"
3. the password is "guest"

and if that doesn't work, try doing workgroup/guest for the user name. I am assuming you have to substitute the name of the workgroup for the word workgroup above.

Re: Problems Connecting to CloudPod - SOLVED

PostPosted: Thu Aug 18, 2022 3:40 pm
by JimODB3000
Lance Lewis wrote:when you go into windows credential manager did you see clouded already listed? If not, when you added it did you verify the following:
1. the spelling of the name is exactly the same
2. the user name is "guest"
3. the password is "guest"

and if that doesn't work, try doing workgroup/guest for the user name. I am assuming you have to substitute the name of the workgroup for the word workgroup above.


Yes, I've done those things as far as I can tell. We are on a Active Directory Domain so there isn't a workgroup or workgroup name that I can reference. When I do add the Cloudpod into the credentials manager, exactly the same spelling, and add useername guest password guest then I get an error that I cannot connect to the Cloudpod because the user account is disabled.

Re: Problems Connecting to CloudPod - SOLVED

PostPosted: Thu Aug 18, 2022 3:42 pm
by JimODB3000
Also, I emailed support on Monday 8/15/22 and haven't received a response yet as of Thursday 8/18/22, I'm not sure if that is typical or not but I'm surprised with no response yet.

Re: Problems Connecting to CloudPod - SOLVED

PostPosted: Fri Aug 19, 2022 6:40 pm
by Jack Fairley
JimODB3000 wrote:
Lance Lewis wrote:when you go into windows credential manager did you see clouded already listed? If not, when you added it did you verify the following:
1. the spelling of the name is exactly the same
2. the user name is "guest"
3. the password is "guest"

and if that doesn't work, try doing workgroup/guest for the user name. I am assuming you have to substitute the name of the workgroup for the word workgroup above.


Yes, I've done those things as far as I can tell. We are on a Active Directory Domain so there isn't a workgroup or workgroup name that I can reference. When I do add the Cloudpod into the credentials manager, exactly the same spelling, and add useername guest password guest then I get an error that I cannot connect to the Cloudpod because the user account is disabled.

If you're on a domain joined machine, try using the username .\guest instead of just guest. It sounds like it's hitting the domain controller for the account and not the box.

Re: Problems Connecting to CloudPod - SOLVED

PostPosted: Mon Aug 22, 2022 5:56 pm
by JimODB3000
Thanks for that recommendation, I think you're right that it was likely hitting the DC and not the local machine, the domain guest account is indeed disabled. I gave that a try in the credential manager by adding the local hostname\guest and the error changed from account disabled to network path not found. I have attached a screenshot. Also, a full week later and still no response from Blackmagic Support.

Thanks,
Jim

Re: Problems Connecting to CloudPod - SOLVED

PostPosted: Mon Aug 22, 2022 7:30 pm
by Jack Fairley
The only other thing that comes to mind would be enabling the registry key that disables the use of guest accounts.

Re: Problems Connecting to CloudPod

PostPosted: Tue Nov 08, 2022 10:46 pm
by danielschmidt
I had a similar problem with a domain-joined computer not being able to connect to the Cloud Pod file share, with Event ID 31013 being logged in the Microsoft-Windows-SMBClient/Security event log.

In our case it was because of Group Policy enforcing the SMB Client security option "Microsoft network client: Digitally sign communications (always)".

A temporary workaround is to open PowerShell as Administrator and run:
Set-SmbClientConfiguration -RequireSecuritySignature $false

This will only last until the next Group Policy refresh though, so it may be necessary to exclude your PCs which connect to the Cloud Pod from enforcing this policy. Obviously this is not a best practice, and hopefully the issue is addressed in a future firmware update.

https://learn.microsoft.com/en-US/troub ... onnections

https://learn.microsoft.com/en-us/windo ... ons-always

Re: Problems Connecting to CloudPod

PostPosted: Wed Nov 09, 2022 7:30 pm
by JimODB3000
I opened a ticket with support and after weeks without response I finally got a reply back.

"In some of our testing, it appears that SMB 1.0 has to be installed on W10 for this to work for initial SMB volume discovery on the network.

We have further inquired about this from our developers. As soon as we hear back, we will follow up with you."


Using SMB 1.0 is insane in today's world, it's not even loaded by Windows anymore because it's so old and unsecure. It seems like they are probably correct though because I manually installed the SMB1.0 service to test and that seemed to allow me to connect to the CloudPod. I can't keep that loaded though, it's too unsecure and our IT department won't allow it.

I hope they can change that to SMB3.0 in a future software release.

Re: Problems Connecting to CloudPod

PostPosted: Wed Nov 09, 2022 7:54 pm
by Jack Fairley
Come on BMD, there's no way SMB 1.0 flies anywhere that is doing vuln scans.

Re: Problems Connecting to CloudPod

PostPosted: Wed Nov 09, 2022 7:57 pm
by JimODB3000
I emailed them back for an update and they got back to me right away that they still have no update from their developers on this issue. It's SUPPORT #SXR-413-34124 if anyone want's to open their own ticket and reference it.

Re: Problems Connecting to CloudPod

PostPosted: Tue Sep 19, 2023 4:57 pm
by Gerdty
Did y'all ever find a fix for this? I'm facing the same issue myself. Getting Error Code: 0x80070035 "The network path was not found"

In my case, the cloudpods work flawlessly on 2 macs that I have on my network, but the PC will randomly lose connection (yielding that error code) and the only way to restore it is to power cycle the cloudpod

Re: Problems Connecting to CloudPod

PostPosted: Thu Sep 21, 2023 1:26 pm
by JimODB3000
Gerdty wrote:Did y'all ever find a fix for this? I'm facing the same issue myself. Getting Error Code: 0x80070035 "The network path was not found"

In my case, the cloudpods work flawlessly on 2 macs that I have on my network, but the PC will randomly lose connection (yielding that error code) and the only way to restore it is to power cycle the cloudpod


As far as I know there hasn't been any changes but I will check the status of my ticket again to see what they say and report back.

Re: Problems Connecting to CloudPod

PostPosted: Mon Sep 25, 2023 8:07 pm
by Gerdty
As far as I know there hasn't been any changes but I will check the status of my ticket again to see what they say and report back.[/quote]


Any luck? Any time I have reached out to Blackmagic support they have pretty much blown me off and not tried to actually help.

Re: Problems Connecting to CloudPod

PostPosted: Tue Sep 26, 2023 2:37 pm
by JimODB3000
Gerdty wrote:As far as I know there hasn't been any changes but I will check the status of my ticket again to see what they say and report back.


Any luck? Any time I have reached out to Blackmagic support they have pretty much blown me off and not tried to actually help.



I'm still waiting for their reply, hopefully I will get a response soon.

Re: Problems Connecting to CloudPod

PostPosted: Wed Oct 04, 2023 1:12 pm
by JimODB3000
Gerdty wrote:As far as I know there hasn't been any changes but I will check the status of my ticket again to see what they say and report back.


Any luck? Any time I have reached out to Blackmagic support they have pretty much blown me off and not tried to actually help.


OK, so I got a very discouraging reply from BMD support.

Hi,

Our developers do not comment directly on items that are submitted to them. All I can say is that it has been reported to them.

Regards,



Adam B

Support Representative

Blackmagic Design Inc.

Ticket Details
________________________________________
Ticket ID: SXR-413-34124
Department: DaVinci Resolve
Type: Issue
Status: Closed
Priority: Normal



So it seems like they know about this issue and are doing absolutely nothing to remedy the situation other than waiting on "their developers".

Re: Problems Connecting to CloudPod

PostPosted: Tue Oct 17, 2023 4:18 pm
by Gerdty
Looks like today blackmagic released a firmware update that claims to solve this issue. I'm working on installing it right now. Time will tell...

Re: Problems Connecting to CloudPod

PostPosted: Tue Oct 17, 2023 5:00 pm
by JimODB3000
Gerdty wrote:Looks like today blackmagic released a firmware update that claims to solve this issue. I'm working on installing it right now. Time will tell...


I'll be curious to hear your findings. I just installed the update on my CloudPod and it did not fix the issue for me. I have domain joined Win11 systems that cannot connect to the CloudPod, I am still getting the 1208 Network error that the update says it resolved.