Some networking help please!!

Hi,
We have 7 clubs in our complex, with 2 iPC and 5 dedicated Hog3PC systems running the lights. I keep all Hog3 systems software up to date. I do not use any DP2000 or DP8000's. All system dmx are connected via widgets or super widgets. I also have 15 PC's running video, lasers, music and some stage mechanics. I have an AV server which we regularly backup the shows on. All the clubs PC's are connected to a fibre linked gigabit network, and have fixed IP addresses, and have access to internet. There are about 100 PC's across the network. The iPC's weren't connected due to issues I had with Hog3 V2.0.x. but I would like to connect them to the network at some point.
I run XP Professional SP3 on Dual Core systems with 2gig ram, Nvidia Quadro video cards & ELO Touch screens. I have Windows firewall off and run norton internet security 2003 & 2009 on the AV PC's.

Previously I had Hog3PC configured to run off the loopback adaptor, and ignore the network connection, so that network going down etc wouldn't affect running of the shows.
I didn't worry about port and net numbers, apart from each Hog3PC having a different port number. They are all running different shows.

I updated our iPC's with full install of v8.3 image, and updated iPC config and hog3pc v3.0.1.
I updated 1 of Hog3PC system to v3.0.0, and then v3.0.1 when it came out. After a couple of weeks of it running smoothly and we are happpy with it I proceeded to upgrade all systems to v3.0.1 b2425.

Instant headache!! Not 1 system would work!! Even the system which had been running for a couple of weeks now would not work!!
The show server would not load. If I said 'ok' to waiting it would try again but would not start. If I said 'no' it would log off to config screen. If I tell it to launch show it would ask me to unlock, then I would have an "fps: " exception and have to restart the software. No change after restart.
I'm sorry that I did not have time to note down the error messages and steps I took to try and remedy it but with the clubs open or opening soon time was not on my side!
I guessed it was due to the new way of dealing with network in v3.0.x so removed all the network connections from all the systems and got all systems to work! PHEW!!!! I haven't reconnected the systems to the network yet.

So... my question is...
How should I setup the Hog3PC networking in this type of system?
What network settings should I use for the iPC's?
I need to used fixed IP's as I stream music and media to other PC's on the network and cannot have an IP conflict.

Regards,
Craig Burridge.
:hogsign: makes us look better!:hogsign:
Parents
  • Hi Ryan,
    The Hog3PC's are dedicated for lighting console...
    I hadn't needed to look into changing network infrastructure before as the system was working properly and did everything I needed... I only use the network for updating windows, hog3pc and antivirus software and show backup on my server.

    The big issue with the network going down, for whatever reason, is that it stops the super widget from working and only a hog3PC software shutdown, widget power cycling and restart of the software gets it working again. pig-open-backspace only shows desktop not responding, which I can restart but it does not get the widget working... I am going to investigate a bit more today if there is other solutions.

    I also think v3.0 is better!
    I am hoping I can configure it to use the loopback adaptor again, because that is a good work around for our systems!

    Craig
Reply
  • Hi Ryan,
    The Hog3PC's are dedicated for lighting console...
    I hadn't needed to look into changing network infrastructure before as the system was working properly and did everything I needed... I only use the network for updating windows, hog3pc and antivirus software and show backup on my server.

    The big issue with the network going down, for whatever reason, is that it stops the super widget from working and only a hog3PC software shutdown, widget power cycling and restart of the software gets it working again. pig-open-backspace only shows desktop not responding, which I can restart but it does not get the widget working... I am going to investigate a bit more today if there is other solutions.

    I also think v3.0 is better!
    I am hoping I can configure it to use the loopback adaptor again, because that is a good work around for our systems!

    Craig
Children
No Data
Related