Check the Hosts file in Windows\System32\Drivers\Etc. Open in Notepad. Is there a LocalHost number in there like 127.0.0.1 or something? The answer is obviously YES, since I see Manager is registering itself as 127.0.0.1. Good. Is there an IP address associated with your machine other than 10.0.0.30?
Open a Command Console Window (Command Prompt in Start, Programs, Accessories, Command Prompt.
Type in: ipconfig \all
Does it list 10.0.0.30 as an IP address for your machine? If Monitor is causing the problem, then are you SURE that you are using the default Port for Manager / Server? Manager port is 3234. Server is 3233. If you changed that, then you need to change what Monitor uses as well to connect to the Manager. Backburner.xml is a text file you can edit to connect to the right Manager. Open that file and make sure it is listing the Manager as localhost, which means, your machine. Or type in the name of your machine, or type in the proper IP Address. Port, leave it to 3234 if you are using the default port for Manager, or change it if you felt crazy and changed it for Manager. The section should be listed as such.
<QueueMonitor> <ManagerName>MANAGER NAME OR IP OR LOCALHOST</ManagerName> <AutoConnect>0</AutoConnect> <AutoSearch>1</AutoSearch> <AutoRefresh>1</AutoRefresh> <NetMask>4294967040</NetMask> <Port>3234</Port> continues
Are you making sure to start Manager first, then once it’s up, starting Server?
Server must be started after manager or it will not find a manager, so it won’t register properly.
Ok
I checked the Hosts file. like you said, it has 127.0.0.1 as local host, also had a little bit on the bottom like this
127.0.0.1 localhost
::1 localhost
tried deleting the line and saving the file, but it didnt make any difference.
Went through the command line and did the ipconfig /all, no other IP address where registered with my computer, just 10.0.0.30.
I have checked and double checked the ports are the defualt numbers.
I went through the xml file and tried using, the IP address, the machine name and localhost, each time i got the same error message as before. At this point i did try changing the port numbers to see if i could get it to work, but nothing did work. The server has no problem seeing the manager on the defualt ports, so i dont understand why the monitor is having so much trouble.
I have tried every variaition possible in regards to which program (manger, server, monitor) is started first, but no combination will work.
I have tried installing an eariler version of backburner (i figured it wouldn’t render the new max 2009 scenes, but that the manager, server, monitor should see each other), and sure enough it all worked fine. server connected to manager, the monitor was able to see the manager and i was able to change server settings via it etc.
Any more ideas? im getting desperate now! cheers for suggestions so far though
Right, leave the Hosts file as you found it. I was just trying to find out if it had an IP Address assigned to your computer name which was in conflict with the current IP Address. This can happen if you have multiple machines on teh network and you use DHCP, where another machine can take over the IP Address. In your case, leave the Hosts file and put back the ::1 you took out.
Did you try disabling User Access Control in Vista?
hi
i changed the file back as soon as it didn’t appear to fix the problem.
I have tried running installs, monitor, server, manager by right clikcing and running as Adminstrator and i have tried after disabling the UAC. i still get the connection error.
I have completly unhooked my PC from network temporarily aswell so that there hopefully wouldn’t be any possibility of it looking at different IP addresses/computers on the network.
HAHAHAHA....YES, i have got it working!!!!
FYI, it was a problem with the wiretap thing. God knows what it’s needed for but i got so annoyed with the monitor not connecting that i started randomly deleting folders from the backburner folder (yes, i know this really isn’t the most sensible approach! )
Anyways after deleting the wiretap folder i booted up the manager (expecting an error to be honest) but instead it registered a new client first and then said the wiretap interface had conected to local manager. I tried connecting the monitor and the manager and hey-presto it started communicating!!!
cheers for the suggestions and help, i guess this was just one of those really obscure errors that was only going to be solved by accident!
Monitor not connecting to manager. I tried to disable wiretrap by renaming cfg-folder, but no success.
I am using backburner for years and never had any problems so far. Connected to computer-name, to ip, to localhost, to 127.0.0.1 and always getting the same error.
Server is starting, connecting to manager and rendering.
)
