Ethernet Error

[Chris Lambrechts]

What happens with only the digirack plugins in there ?

You could move all plugins to the unused folder and just leave the mixer plugins in there if you want.

Make sure you trash your prefs (DAE / digisetup) when you do this.

Do you still get the error ?

if so then I would seriously start considering a clean install. I would even go for a COMPLETE clean install. starting with the OS.


Yes I know ... a hassle ... well ... try a new admin account first if you like. Keith already proposed to do that in a previous reply but in the end there's no 2 ways around it and often with these things ... instead of searching for 72 hours and still not finding what the exact cause is, you may as well at some point bite it and go for a clean / fresh install. It will save you time in the end.

Definitely try the digirack plugins only first. if that solves it you most likely have a plugin causing trouble.


Chris

[DigiTechSupt]

What, exactly, was the beta test you were doing originally?

I'm really not sure what's causing the problem. Have you tried a new admin account? If not - you should. That will help narrow down the problem.

Also, have you tried connecting the D-Command to the computer directly, to rule out a problem with the hub? You might just try resetting the hub as well.

A firmware reset of the D-Command may fix it, if it's corrupted somehow:

http://www.digidesign.com/index.cfm?...0&itemid=21606

Lastly, an uninstall/reinstall of Pro Tools may help - it could be a corrupted D-Command profile. Do a clean uninstall, restart and reinstall then test again.

[Mark Wheaton]

I will try the steps here, when I return next week. I would rather go through the whole clean install then do the process of elimination with plug ins, because I am a working studio and it takes time for this error to show up sometimes. I can't afford to run on reduced plug ins for days until I see a pattern, but I will approach the reinstall idea. Thanks

[netnoggin]

I don't know that I would go to all the trouble of a reinstall just yet. It may actually be saying what it means - ethernet error. Make sure things are good in this department. Some things to check:

1. Make sure the ports are lit up. Your computer and the D-Command should both have LEDs or lights next to the ethernet jack, and they should be lit.

2. As noted in the previous reply, if you are using a switch or hub in between the computer and D-command, try eliminating it and temporarily put an ethernet crossover cable between the two. A standard patch cable won't work - it's gotta be a crossover.

3. I can't speak for the D-Command, but the Control 24 does not require anything but the Digidesign driver in the list of items under Network Properties on the PC. No Client for Microsoft Networks, no Internet Protocol (that's right, no IP at all), etc. You could uncheck all of those except the Digi driver just to eliminate them from the equation. Of course, this means your PC will not connect to anything else, but if it's a standalone installation and the D-Command is the only thing hooked to it, no problem. Note you don't have to delete them, just uncheck them. That way you can easily reinstate them if you desire.

It's also possible that your ethernet port on your PC is getting intermittent. Not likely, but possible. Remember the troubleshooter's mantra:

"When you have eliminated the impossible, whatever remains, however improbable, must be the truth." - Sir Arthur Conan Doyle

[Mark Wheaton]

This problem has resurfaced.

I upgraded to PT 8 and installed on a new drive, new system, installed PT 8 fresh, went through my plug ins and made double sure all were up to date. I was not seeing the ethernet error anymore.

Then after upgrading to the cs2 version, when I quit Pro Tools or crash and do not restart, I get the same old ethernet error described above, followed by the Satellite network error. (I do not have the Satellite feature, but I do have a D-Command on a brand new ethernet hub)

Keep in mind this happens even after a Quit with no crashes involved. And it happens 100% of the time if you relaunch without a restart.

I have screen grabs of the errors if needed.
The only solution is a restart of both the computer and the D-Command.

[Mark Wheaton]

Is there anyone else seeing this issue?

[RobSi]

Mark,

When you go back into the Peripherals dialog for Ethernet Controllers, is the correct Ethernet Port selected? Or does it switch to a different port that the cable isn't plugged into?

Cheers,

[Mark Wheaton]

I will check this and get back, thanks

[Boe Larsen]

Hello there.
Have the same sort of problem with my system on PT8. When the system crashes (happens once in a while with audio instruments) I loose the connection to the D-command, and I can only get it back by restarting the computer.
Any news on the subject?

Best,
Boe

[Mark Wheaton]

I have not had to quit and restart over the last week, so I have not had the problem. I will try this again today and report back.