Inside Sabertooth
Learn how Sabertooth uses 3ds Max to create 3D interactive projects, including HBO Go’s Game of Thrones interactive experience
  • 1/3
You are here: Forum Home / Autodesk 3ds® Max® / Autodesk 3ds Max / 3ds Max Design 2009 / backburner error after switching to gigabit switch
  RSS 2.0 ATOM  

backburner error after switching to gigabit switch
Rate this thread
 
14019
 
Permlink of this thread  
avatar
  • Total Posts: 23
  • Joined: 12 May 2008 11:13 PM

I just bought a Linksys gigabit switch to replace my old 10/100 switch. Copying files over the network works beautifully - no problems there. HOWEVER - when I try to submit a network rendering job it no longer works. It says “error message: File I/O error with job archive”. If you then go & try to open the ZIP file of the project in the backburner network job folder it is corrupted every time (on the original manager computer the zip file is OK). As soon as I switch back to the 10/100 switch the problem goes away.  Any thoughts what this could be ??



i7 920 GTX480 + 2 x GTX280 Win7 x64 12gb Ram 1200Wpsu. 5 x i72600 farm

Replies: 0
avatar

Leo,

I stumbled upon your post whilst pulling my hair out over the same issue. I thought something was up with Backburner. However, I too recently upgraded to a gigabit switch, although mine is a D-LinkoDGS-2205. As soon as I took it out of the mix, all returned to normal! Thanks!

But I must ask, did you ever find a solution as to why it was corrupting files?



Graham Calhoun
President
Forensic ProMedia

Replies: 0
avatar

that reminds me, I should always make a record of how problems are solved, because I dont think I can remember how this issue was resolved ( I am using the gigabit switch without any hitches now).  It might have been something to do with my IPv4 settings. Resetting them may have helped the problem (before they were custom settings instead of “obtain IP address automatically”. If i do recall anything more concrete i will make another post.



i7 920 GTX480 + 2 x GTX280 Win7 x64 12gb Ram 1200Wpsu. 5 x i72600 farm

Replies: 0
avatar

I’d like to add my own findings on the same issue.
I didn’t change my switch or router, didn’t use an xreffed camera and didn’t have long camera name.
What I did do was add my laptop to the render farm - where it spat those errors.
However - this laptop usually is connected wirelessly - this time I added it to the farm with a cable. Turns out - if I don’t disable the wireless connection then I get these errors. It was connected with two connections - wired and wireless - so that might explain why sometimes it would render fine and sometimes not.
Now that I’ve disabled the wireless connection it works fine.

My 2 cents



Replies: 0