Help With Access Control Losing Connection To Event Server

Are there any logs on the event server to look at other than the connected/disconneted on that interface?  Just throwing out an oddball idea, is the C Drive on the Event Server full or nearly full? 

Just tossing in ideas here.

I would start with any and all power settings.  Check the OS, check the NIC etc. It could be a form of sleep mode.

I agree you should try running wireshark.  Does it connect long enough to do anything or is just just re-attempting connections?  Sorry to ask but have you checked the ip address, subnet masket, etc. to make sure you're really connecting between the server and the panels.  Also you say you swapped boards but did you swap the cables with a known working set of network cables.  Is there some sort of config tool or device discovery utility or something other than the pacs server you could use to attempt to connect to the panels (to see if they'll talk to anything at all.)  Good luck!

More thoughts:

Did you check Windows Firewall settings? They're a little bit different in Windows 10 vs 7?

Also what is the model of the controller? I found this googling for possible fixes related to Galaxy Control Panels:

NOTE: The Ethernet connection MUST be a 10Mb connection, NOT a 100Mb connection

 Is there a password required to connect the panel? It almost looks like a bad login type loop on a system, where it connects, cant authenticate, and then tries to reconnect (obviously without a discrete "Bad login" type of error).

10 megabit only?  Really?  Can you even buy 10 megabit only ethernet chips any more?  That went out of style along with Flock of Seagulls.

But um yeah if a modern hardware device was attempting to talk 10 megabit by "autosensing" the speed I suppose you could get some sort of wonky effect like that.

If you need to check 10 megabit vs faster also look for if it's 10 megabit half duplex.

So it ended up not being a Windows 10 issue.  We were asked to uncheck QoS and QoS scheduler and to uncheck IPV 6.

I admit I do not know exactly what those settings turned off.  

We had already changed the speed to 10 megabit.

Thanks everyone for your help.  I didn't get a chance to use wireshark.  I had some other things come up.

Tom

btw that is the current Galaxy hardware.  I don't know what the decision making process is on the 10 mb chip is.  Maybe a reliability, durability, compatibility , or financial decision.  Chime in with your thoughts if you like.  I would be interested in knowing why.

unchecking QoS and Ipv6 as a fix doesn't make sense (but glad you're on the air.)

Unchecking Ipv6 in windows makes it stop using that protocol.  If Ipv6 and IPv4 are both enabled a machine will seek out the IPv6 infrastructure first.  that can be an issue.  Unchecking QoS should do nothing unless you had QoS on your switch.

I am going to take a look at the laptop and see what those settings are.  I was told it was a windows 7 laptop.  I am finding that it is actually a windows 10.  I did not see it or connect it.  I was simply told that is what they had.  I suppose that's what I get when I am brought in to help after they have tried several other things.

Thanks,

Tom

Everything is fixed and good here.

I read a lot of issues on boards that seem to end without a final report.  So here is my report.  The issue was not with Galaxy or Windows 10.  It ended up being a setting on the NIC card.  I had help from my techs here, the people on this board, and Galaxy.  Galaxy support supplied the final answer that alleviated the issue.  I want to thank everyone involved.  The wealth of information shared on here has helped me immensely and I will continue to share.  

Tom

Tom,

Thanks for the update, I'm glad the case is resolved for you.  Out of curiosity, what setting on the nic was causing the issue? I was assuming it was a power saving setting on the nic. 

Interesting, hard to know since you tried it with so many different computers.  (Unless they all had the same AV software).  On a side note, I've found with weird network issues that resetting the tcp/ip stack resolves a lot of issues.  Obviously this is like nuking the network connection and requires a reboot when flushing dns resolves problems without a reboot.  But if you have network issues and you ruled out AV software and you don't want to go down a long list of things to try, resetting the tcp stack works well.  

Directions:
1. Run elevated Command Prompt:
2. Type: netsh winsock reset
3. Type: netsh int ip reset  
4. Restart the computer

If your network card had a static ip, you'll need to go back in and reconfigure. 

Cheers,