 I received a DigiDelivery email, but neither of the links (for the file ...
|
| I received a DigiDelivery email, but neither of the links (for the file or the DigiDelivery Client) seem to work. |
Please click here for more info, or to download the DigiDelivery Client.
[Page View]
|
|
|
DigiDelivery account passwords are not restoring properly from an account ...
|
| DigiDelivery account passwords are not restoring properly from an account list backup. |
In some cases simply restoring the account list twice will solve this issue.
DigiDelivery may not restore the encrypted passwords correctly if the accounts are not already created on the server.
If the server has no accounts on it, the first restore will create the accounts, and the second restore will import the passwords correctly.
[Page View]
|
|
|
When I use "Send to DigiDelivery" and quit Pro Tools once the file transfer ...
|
| When I use "Send to DigiDelivery" and quit Pro Tools once the file transfer has started, the transfer fails right before it completes. |
This is a known issue in Pro Tools LE 7.4 on Mac OS X.
The workaround is to drag and drop the session folder from a Finder window into DigiDelivery, then choose to send.
[Page View]
|
|
|
How do I configure my DigiDelivery server for use with a Netopia Cayman ...
|
| How do I configure my DigiDelivery server for use with a Netopia Cayman router? (3346n, etc). |
First, you must reconfigure the web server section of the router according to these instructions:
http://www.netopia.com/support/hardware/technotes/Popup/PUWwebsrvr.html
This will allow for a Port 80 pinhole (also known as a NAT rule) to be created for the DigiDelivery server.
After that step is completed, log back in to the router according to the instructions on that page, then follow the instructions on this page to complete pinhole (NAT rule) setup:
http://www.netopia.com/support/hardware/technotes/CQG_025.html
You will need to create pinholes for the following protocols:
Port 22 - tcp
Port 25 - tcp
Port 53 - tcp/udp
Port 80 - tcp
Port 123 - udp
Port 443 - tcp
Please note - you have to use a different Pinhole Name for each protocol.
[Page View]
|
|
|
Unable to view Local Contacts in Outlook 2000's Address Book when sending ...
|
| Unable to view Local Contacts in Outlook 2000's Address Book when sending a DigiDelivery. |
|
This is a known limitation with Outlook 2000.
[Page View]
|
|
|
DigiDelivery Servers and the upcoming changes to Daylight Savings time. ...
|
| DigiDelivery Servers and the upcoming changes to Daylight Savings time. |
We are aware of the upcoming changes to Daylight Savings, and are currently working on an update to accommodate for this. Please check the software updates section of your DigiDelivery server for the most current version of the server software that will include this update.
Until an update is released the reporting and timestamps on emails, etc. will be off.
One workaround is to make sure your workstation time is accurately set, then login to the server as the admin, choose "Date and Time settings", click Edit, turn off "Use Network Time Service to Synchronize Clock" and then click the button to "set server time to same time as browser machine".
DigiDelivery Product Info
[Page View]
|
|
|
Specifications for DigiDelivery Serv|LT and Serv|GT.
|
| Specifications for DigiDelivery Serv|LT and Serv|GT. |
Dimensions: 1.7"h x 17"w x 18"d (1 rack unit)
Weight: approx. 25 lbs
Power Consumption: ~2.72 Amps at 110V (300 Watt power supply)
[Page View]
|
|
|
"Send Via DigiDelivery" does not start a new delivery when attempting ...
|
| "Send Via DigiDelivery" does not start a new delivery when attempting to send a session from Pro Tools |
This can happen if the "&" character is located in the name of the session or an audio file in the session.
DigiDelivery will launch and prompt you for additional items to include in the delivery as normal, but a new delivery is not started.
To resolve this, remove the "&" character from the session name and/or any audio files in the session.
[Page View]
|
|
|
"Cannot find bean certificate in any scope" error when importing SSL certificates. ...
|
| "Cannot find bean certificate in any scope" error when importing SSL certificates. |
This can occur if there is any trailing space in the certificate text.
Workaround: Import with no extra space at the end of lines and no extra lines after the "-----END CERTIFICATE-----" line.
[Page View]
|
|
|
Cannot access DigiDelivery Server login page via LAN 1 or LAN 2. HTTP ...
|
| Cannot access DigiDelivery Server login page via LAN 1 or LAN 2. HTTP 500 Error when accessing Server Login page. |
Symptoms: When attempting to login to the DigiDelivery Server Login page you get "HTTP 500 Error" in your browser window regardless of what port you attempt to connect on (LAN 1 or LAN 2). The Server's LCD screen is stuck at "All network tests passed" and does not go to "Ready" as it normally should.
This is an indication that there could be an issue with the Servers Host Name setting or there is no "Reverse Lookup" in DNS for the servers IP address.
To get around the problem, disconnect both the LAN 1 and LAN 2 ports and reboot the server using the power button. While the server is rebooting it will fail all network tests - this is because LAN 1 is disonnected, let it finish the testing procedures and wait until the server has fully started up.
After the startup routine is finished connect LAN 1 (and if you'd like, LAN 2) and see if you can access the Server login page.
If you still can't access the login page then you may need to contact Digidesign Technical Support.
If this procedure allows you to access the page then a couple of things need to be checked (make sure you login as Admin to check these settings):
1. Check the 'Host Name' setting in the 'Network Information' section. If it is currently set to "localhost" then try changing this to "localhost.localhost" (without quotation marks) and reboot the server via the Reboot Server link in the 'Server Administration' section (leave LAN 1 connected). The server should fully restart and the LCD screen should eventually say "Ready", this may take a few minutes.
2. If the 'Host Name' field is set to anything besides localhost or localhost.localhost then you will need to do an nslookup on the servers IP address and see what host name is currently registered for the IP address of the server. If this does not match you will want to change the Host Name field to localhost.localhost in the DigiDelivery server under 'Network Information' until you can get this resolved with your ISP. Once a host name has been properly registered with your ISP you can set the 'Host Name' field from localhost.localhost to the registered host name.
More Info:
Ideally you want to have a registered host name for your DigiDelivery Servers IP address. This can be done through your ISP. It is also recommended that there is a "reverse lookup" registered for this IP address, so the host name can be resolved from the IP address and vice versa. The best scenario is to have a registered host name for your servers IP address and to have the 'Host Name' field in the DigiDelivery server set to this name. If there is no registered host name or you are unsure, it is best to set the Host Name field in the server to "localhost.localhost".
[Page View]
|
|
|
