Major networking problems with PC server and my brand new road hog

v 3.1.0(b1078)
driver version 3.1.00.224
Qt version 4.7.0
OS version windows 6.2
Processer type intel(r) core TM i3-3217u cpu @ 1.8 GHZ
i can't get my road hog to consistently see my server . I log off and unplug and move all day . then re log into the show, the Road hog console does not see my server.
also, my server crashes about once every 2 hours. Im rigging for the next week but start show soon . please help.
driver version 3.1.00.224
Qt version 4.7.0
OS version windows 6.2
Processer type intel(r) core TM i3-3217u cpu @ 1.8 GHZ
i can't get my road hog to consistently see my server . I log off and unplug and move all day . then re log into the show, the Road hog console does not see my server.
also, my server crashes about once every 2 hours. Im rigging for the next week but start show soon . please help.
Comments
I had paid attention to that when i started her up again but did not reboot properly to change it .The thing that threw me is the spotty connection.
I also took Hog 4 off my PC then put it back on. have no idea if that helped fix it or not.
I had no other hardware between my server and Lap top except Cat6 cable
I worked on my Road hog and saved to thumdrive,Loaded it on to server.
Crashes were not total crashes, just screen freeze while i was working on the connection issue
It ended up connecting solid at the end of the day , i logged off and rebooted numerous times
Thank you
I had paid attention to that when i started her up again but did not reboot properly to change it .The thing that threw me is the spotty connection.
I also took Hog 4 off my PC then put it back on. have no idea if that helped fix it or not.
I had no other hardware between my server and Lap top except Cat6 cable
I worked on my Road hog and saved to thumdrive,Loaded it on to server.
Crashes were not total crashes, just screen freeze while i was working on the connection issue
It ended up connecting solid at the end of the day , i logged off and rebooted numerous times
Thank you
What is the IP of your RH?
Do you have anything else on the network?
OK now on to the monitor problem, is this a touchscreen monitor?
Can you provide the monitor type, manufacture and model type and part number?
What do you mean by will not boot up?
Launcher never appears?
https://yadi.sk/i/COdUG6FFi9GYv
Road Hog 4 client
Version 3.0
Hog PC Main server
niyaz said exactly the same thing thats happening to me. It happens with all external monitors I try. If the console is OFF at the switch then turn ON at the switch, the console sends error texts and Highend splash screen will not even come on.
disconnect the monitor, the hog starts up.
At this point I can connect the monitor and a small blip happens on the screen while I connect it.
I connect to my show and bring up my view and everything is fine.
a work around i guess
What is the exact monitor you are using?
Need the model and part number.
and to keep with my original post about networking , when i upgraded to 3.2
i made sure to reinstate my ip addresses
I installed system everything fine all ( except being able to log off as a client)
All ips were correct
then ... ran my show for 2 days and noticed somehow my road hog had the default ip of 127.31.0.1 and still logged on to my server with the ip of 192.168.185.1
DHCP was off
( this is after upgrade to 3.2) re imaged from Linux stick
I had total control over my show for 2 days
and the ip addresses were totally out of range of each other .
admitting Im not the most knowledgable of all things , but I know thats kinda weird , don't you think?
Hog PC server 3.2
2 netgear 1000mbs unmanaged switches
1 beloved Road hog
1 dell E2014T out of VGA output on road hog
thank you for your patience and support
~:> ~:> I swear Im not related to chicken little
You are correct some monitors that are not listed in our manual will in fact work but have not been tested.
The ones listed in the manual have been fully tested.
The client log off was a defect that has been fixed in the 3.2.1 release.
Normally when you see a 127 ip it means a network cable is not plugged.
Hate to ask but are you sure you looked at the HogNet tab and not the FixtureNet tab?
The 127 IP was seen on the RH and not on the PC?
and was in Hognet network tab.
Is your network solid now or are you still having problems?