WOW!!! Same problem

Thanks!!

Still having the problem with Manager, it’s never “shutdown” properly.

I’m having a terrible time getting the monitor to connect to the manager. The ‘wiretap’ rename used to work for me but now it won’t.

One thing I’m seeing going on is that when I click to ‘Connect to Manager’ I can enter a ‘Manager Name or IP Address.’ It is holding the IP address of my LAN. I’m trying to connect through my new Wireless Router which assigns its own IP address to the machine. Using the machine name used to work but doesn’t now. I still think it won’t let go of the LAN IP address that isn’t being used.

If I type in the new IP address the field won’t hold it. It reverts back to the wrong IP Address. Where is the Manger storing the IP address so I can manually change it? If I use ‘Automatic Search’ it displays the correct Subnet Mask but fails to connect also.

---------------------------------------------------------------
Windows 7 Professional x64 - Asus P9X79 Pro - Intel i7-3960 Extreme - 16GB Kingston HyperX DDR3 1600 - Corsair H80 Chiller - Nvidia Quadro 4000 - 3D Studio (preMax) thru Max 2013 Design

Don’t you just love it when Autodesk includes broken files with the install? Do they not test these things? Anyways, this solved my problem.

Though, I still have to task manager kill process if I want to shut the backburner manager down. That’s brilliant. I got tired of doing it, so I wrote a batch file to kill it for me. I bet the Autodesk software engineers wear Velcro shoes because laces just seem to be too complicated for them.

I started to have the same problem where I did not have before. I see an IP address (127.0.0.1 ) on my manager window, which I also see on yours. I’m not exactly sure if that address existed before, but if it existed, I believe I would remember.
To control the net render jobs, I ran the Monitor on a server node running Windows XP. No comm. errors on that machine and worked fine.

Is it possible that monitor is looking for the manager at 127.0.0.1, instead of my local host, and which hardware does that 127.0.0.1 belong to?
Is it another net adapter line bluetooth PAN, or a 1394 device, or a soft driver that uses that virtual address to handle something?
Any ideas?

127.0.0.1 is a loop back address, it’s the local host, a machine will look at it’s self with that address. You should manually type in the correct address for the machine that runs Manager.

Oh I see.

By the way, it seems that the problem is not with the Monitor but with the Manager on my local machine. I started manager on another node, and the monitor on my local machine connected to this one without problems.

And there is something different with the manager on my machine: when I shut it down, it doesn’t shutdown as normal. It says not responding for sometime and I have to terminate it.

My problem still exists after I tried all the ideas above.

I have a problem with Windows system as well. Personalize window doesn’t open, and it’s represented with a normal folder icon on Control Panel. It happened during a hard drive corruption a few weeks ago. I feel I need to repair several files of Windows as well.

Original Vista CD repair option doesn’t find anything to repair. Do you know any other way to repair windows system files by copying intact versions of them? I can’t also restore my computer to some earlier date.

What a crazy problem this is!!

Monitor on my local machine doesn’t connect to the manager on this machine.
But it connects to another manager on the network.

So it seems there is a problem with the manager, not the monitor.

But the monitor on some other machine can connect to the manager on my local machine.
So it seems there is a problem with the monitor, not the manager.

In fact net render works. Only I can’t monitor on my local machine because of communication problems.

I believe it’s a problem with Windows itself:)

Many many many thanks for solving this problem.  I just deleted those two files and the monitor found the manager just fine.