Jump to content
AutoDesSys Forums
Spacer

Network problem- under deadline and unable to network render..

Recommended Posts

Hi,

 

I have 2 PC's under Win 7. I cannot get the Network rendering to work.

 

Monitor from one Machine sees the Node in the other(and it's "own node".

 

In the past I had this working, but I moved the PC's and changed some settings- don't ask which...

 

Info:

 

  • Both have internet
  • Some of file sharing works fine, other not
  • All versions of Maxwell 3 are latest and the same
  • FZ v8 lastest
  • 64bit machines
  • Residential network
  • Monitir sees the Node and Node even shows 'New Job Order Received" , but NO Progress in rendering on the Node while the Node on the Monitor machine chugs along and advances SL. The Node machine nevergets beyond "New Job Order Received".
  • In the Monitor it says the distant Node is"Rendering" under status, bu tnever shows progress or an SL at all.
  • Tried a very simple model and nada..
  • IP's are automatic,bu t I am having trouble making them fixed (I had been able before) in IPV4. Once I configure, and click "OK" it opens a network problems window and resets my IPV4 to "automatic". It may be when I try to put in DNS ..I am  not sure how to to that. Are th eDNS values the same on both machines?
  • I have IPV6 active but am not sure I should touch that configuration.

I am dying here. Under deadline and cannot debug this network.

 

Both machines are cabled by ethernet into a router that my ISP gave me,and this has worked in the past.

 

At this point, I'd pay someone to help..

 

Best

Peter

Edited by Spacer

Share this post


Link to post
Share on other sites

I even made sure the 4temp' folder for MXnetwork was shared and visible for each computer on the network of the other.

 

THe render is still not happening.

 

Share this post


Link to post
Share on other sites

I have added exceptions in AVG/avast

I have tried to make sure firewall has all the right exception

I have tried to render with firewall dis-abled, etc...

 

still the same exact reaction.

Edited by Spacer

Share this post


Link to post
Share on other sites

Hi Spacer,

 

Here's a direct link to the Network Troubleshooting page, which has some good information:

http://support.nextlimit.com/display/mxdocsv3/Network+troubleshooting

 

I would help directly if I could, but this is not an area where i have any expertise. You might submit a help ticket through the Maxwell portal, or visit the Maxwell network rendering forum. This really sounds like a network / firewall / antivirus issue, though.

 

 

Share this post


Link to post
Share on other sites

I get the same Error as a few years ago:

 

"QWidget: Cannot create a QWidget when no GUI is being used"

 

At least now the Node starts rendering, but it fails...with the above warning.

Share this post


Link to post
Share on other sites

The orange text would indicate that your MXI filepaths are mangled, you might want to investigate that...

 

I recommend submitting a help ticket through the Maxwell portal, or visit the Maxwell network rendering forum.

Share this post


Link to post
Share on other sites

I noticed some files began with double lower dash "__", but then on another file which didn't have this the network render crashed as well.

 

My temp folders are empty after the crash of the Node also.

 

I amstarting to want to cut my losses and find new reliable software to render with....ugh...

Share this post


Link to post
Share on other sites

Spacer,

 

I am sorry for your frustration. All I can say is, the Maxwell network renderer normally works fine. There is something wrong with your network or setup. Again, I recommend that you contact the proper people: Maxwell tech support by submitting a help ticket through the Maxwell portal.

Share this post


Link to post
Share on other sites

Hi,

 

I have fixed it. Mihai at NL saw that i had an "apostrophe" in my computer's name (my last name is O'Brien) and that it messed with the paths. I renamed the Node computer and cleaned up that mess and it works now..

 

thanks again-

 

Peter

 

Share this post


Link to post
Share on other sites

Hi,

 

I have fixed it. Mihai at NL saw that i had an "apostrophe" in my computer's name (my last name is O'Brien) and that it messed with the paths. I renamed the Node computer and cleaned up that mess and it works now..

 

thanks again-

 

Peter

 

Share this post


Link to post
Share on other sites

It boggles my mind that some 40 years after computers became widely available that there are still limitations and issues with special characters in file names. The modern UI should never be held hostage by legacy code inadequacies.

Share this post


Link to post
Share on other sites

Thanks Setz for th e moral support. It cost me 20 hours of fiddling and sweating time which could have been spent finessing my work!!

 

A friend told me to go Linux, I may just do it.

Share this post


Link to post
Share on other sites

Thanks Setz for the moral support. It cost me 20 hours of fiddling and sweating time which could have been spent finessing my work!!

 

A friend told me to go Linux, I may just do it.

 

Justin is also sorta right, I should have known this, but I didn't..

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×