Collision Domain - In POS



  • @WrCombs said in Collision Domain - In POS:

    @IRJ said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    They are having a huge issue when their busy, and all terminals are in use, where they will start to freeze for a few seconds, its only a problem when they are running more than one terminal on either side of the bar.
    If their using 2 terminals on the same side of the bar it runs a little bit faster but there's still a delay.

    Is this really the issue or is this what you are being told? End users are wrong alot, and not always intentionally.

    With how small that network is there is no way there is a bandwith issue from using POS terminals.

    Also your diagram is probably inaccurate, I doubt they have 3 separate switches for 6 systems.

    no there are 3 separate switches.. One on either side of the bar, and one in the back office that feeds to the firewall and the sever.

    Not ideal, but it should still work that way.

    I think investigating at the OS level would be best. I doubt it doesnt only happen when its busy. Its only when they care or notice the delay.



  • @IRJ said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @IRJ said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    They are having a huge issue when their busy, and all terminals are in use, where they will start to freeze for a few seconds, its only a problem when they are running more than one terminal on either side of the bar.
    If their using 2 terminals on the same side of the bar it runs a little bit faster but there's still a delay.

    Is this really the issue or is this what you are being told? End users are wrong alot, and not always intentionally.

    With how small that network is there is no way there is a bandwith issue from using POS terminals.

    Also your diagram is probably inaccurate, I doubt they have 3 separate switches for 6 systems.

    no there are 3 separate switches.. One on either side of the bar, and one in the back office that feeds to the firewall and the sever.

    Not ideal, but it should still work that way.

    I think investigating at the OS level would be best. I doubt it doesnt only happen when its busy. Its only when they care or notice the delay.

    Probably accurate.



  • I have to ask the dumb question. How are tablets being connected to a wired network?



  • @WrCombs said in Collision Domain - In POS:

    apparently, Our Des Moines Office did this setup , we did the other sites set up which would be inconsistent on our end. My boss is claiming that Their image was broken, and we fixed it in house before it went out to the site, which would mean, Scott, You're correct that it's a Server issue.

    This kind of just comes with experience. Can a network be the issue here? Sure, of course. But is it likely? Not at all. Both the "how could these machines overwhelm a network" aspect as well as the behaviour. It was acting like a congested server, not network. With experience you start to "feel" how the system is reacting and nothing really does that other than a combination of understanding as many of the components as possible, and just experiencing loads and loads of different conditions.



  • @IRJ said in Collision Domain - In POS:

    End users are wrong alot, and not always intentionally.

    But very often intentional!



  • @WrCombs said in Collision Domain - In POS:

    @IRJ said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    They are having a huge issue when their busy, and all terminals are in use, where they will start to freeze for a few seconds, its only a problem when they are running more than one terminal on either side of the bar.
    If their using 2 terminals on the same side of the bar it runs a little bit faster but there's still a delay.

    Is this really the issue or is this what you are being told? End users are wrong alot, and not always intentionally.

    With how small that network is there is no way there is a bandwith issue from using POS terminals.

    Also your diagram is probably inaccurate, I doubt they have 3 separate switches for 6 systems.

    no there are 3 separate switches.. One on either side of the bar, and one in the back office that feeds to the firewall and the sever.

    This feels crazy. So much to fail and so much hardware. All to save like... two wires?



  • @travisdh1 said in Collision Domain - In POS:

    I have to ask the dumb question. How are tablets being connected to a wired network?

    Access point on the firewall routed to the wired network.



  • @scottalanmiller said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @IRJ said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    They are having a huge issue when their busy, and all terminals are in use, where they will start to freeze for a few seconds, its only a problem when they are running more than one terminal on either side of the bar.
    If their using 2 terminals on the same side of the bar it runs a little bit faster but there's still a delay.

    Is this really the issue or is this what you are being told? End users are wrong alot, and not always intentionally.

    With how small that network is there is no way there is a bandwith issue from using POS terminals.

    Also your diagram is probably inaccurate, I doubt they have 3 separate switches for 6 systems.

    no there are 3 separate switches.. One on either side of the bar, and one in the back office that feeds to the firewall and the sever.

    This feels crazy. So much to fail and so much hardware. All to save like... two wires?

    I understand that too.. I'd think it'd be better to have each terminal have it's own line to a single switch in office server..



  • @scottalanmiller said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @scottalanmiller said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @scottalanmiller said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    So it's not a collision Domain because their Obsolete in wired networks due to switches -

    I'm not sure what else could be causing the issue other than bad cabling/ Bad terminals/ Bad switches.
    May be worth replacing the other bar switch and changing out the Cabling under the bar.

    So start with the basics and see what you can track down. If you are getting congestion or bad switches / cabling, you'd expect to see it even with a ping. Ping from device to device and see if you ever get latency or drops. If not, likely it's not a networking thing.

    Can you describe the freezing? Like if you do X which devices freeze. And if you do Y, these other devices freeze.

    Only information I have is " when we're Busy, and we try to order items on the terminals they run slow and freeze up. then it comes back then it shows up. the delay is anywhere from 15 seconds to 2 minutes"
    Nothing specific when it comes to what their doing on the terminals.

    Any reason that there is a network suspicion then, why not suspect the server?

    Cause it's the exact same image/setup as the other site they have, and the other site doesn't run slow what so ever.

    Still, many times more likely to be a hard drive or something.

    This. Something like that trans.log is being written to a single 5400 RPM drive.



  • @WrCombs said in Collision Domain - In POS:

    @scottalanmiller said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @IRJ said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    They are having a huge issue when their busy, and all terminals are in use, where they will start to freeze for a few seconds, its only a problem when they are running more than one terminal on either side of the bar.
    If their using 2 terminals on the same side of the bar it runs a little bit faster but there's still a delay.

    Is this really the issue or is this what you are being told? End users are wrong alot, and not always intentionally.

    With how small that network is there is no way there is a bandwith issue from using POS terminals.

    Also your diagram is probably inaccurate, I doubt they have 3 separate switches for 6 systems.

    no there are 3 separate switches.. One on either side of the bar, and one in the back office that feeds to the firewall and the sever.

    This feels crazy. So much to fail and so much hardware. All to save like... two wires?

    I understand that too.. I'd think it'd be better to have each terminal have it's own line to a single switch in office server..

    Yes, one switch that's cheaper than three, easier to manage, less to fail, fewer hops, fewer patch cables and just two more longer runs in the walls.

    Cheaper in every way. Even in electric. And takes up way less space around the office.



  • @scottalanmiller said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @scottalanmiller said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @IRJ said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    They are having a huge issue when their busy, and all terminals are in use, where they will start to freeze for a few seconds, its only a problem when they are running more than one terminal on either side of the bar.
    If their using 2 terminals on the same side of the bar it runs a little bit faster but there's still a delay.

    Is this really the issue or is this what you are being told? End users are wrong alot, and not always intentionally.

    With how small that network is there is no way there is a bandwith issue from using POS terminals.

    Also your diagram is probably inaccurate, I doubt they have 3 separate switches for 6 systems.

    no there are 3 separate switches.. One on either side of the bar, and one in the back office that feeds to the firewall and the sever.

    This feels crazy. So much to fail and so much hardware. All to save like... two wires?

    I understand that too.. I'd think it'd be better to have each terminal have it's own line to a single switch in office server..

    Yes, one switch that's cheaper than three, easier to manage, less to fail, fewer hops, fewer patch cables and just two more longer runs in the walls.

    Cheaper in every way. Even in electric. And takes up way less space around the office.

    Exactly my thought on it too, but, Hey, Who listens to a guys who's been around for 2 years?



  • @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    I have to ask the dumb question. How are tablets being connected to a wired network?

    Access point on the firewall routed to the wired network.

    FFS, there is the issue.

    I know you normally have a network dedicated to POS. That doesn't magically free up availability for the wifi network when things get busy. The wireless environment is probably clogged full when the place gets busy. That'll be your bottleneck.



  • @travisdh1 said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    I have to ask the dumb question. How are tablets being connected to a wired network?

    Access point on the firewall routed to the wired network.

    FFS, there is the issue.

    I know you normally have a network dedicated to POS. That doesn't magically free up availability for the wifi network when things get busy. The wireless environment is probably clogged full when the place gets busy. That'll be your bottleneck.

    FFS explain what you mean? Nothing you just said makes any sense to me.

    The Tablet is Not Currently in Use.



  • @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    I have to ask the dumb question. How are tablets being connected to a wired network?

    Access point on the firewall routed to the wired network.

    FFS, there is the issue.

    I know you normally have a network dedicated to POS. That doesn't magically free up availability for the wifi network when things get busy. The wireless environment is probably clogged full when the place gets busy. That'll be your bottleneck.

    FFS explain what you mean? Nothing you just said makes any sense to me.

    The Tablet is Not Currently in Use.

    You've been talking about the wired network, but the tablets that are having issues aren't even connected to it.



  • @travisdh1 said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    I have to ask the dumb question. How are tablets being connected to a wired network?

    Access point on the firewall routed to the wired network.

    FFS, there is the issue.

    I know you normally have a network dedicated to POS. That doesn't magically free up availability for the wifi network when things get busy. The wireless environment is probably clogged full when the place gets busy. That'll be your bottleneck.

    FFS explain what you mean? Nothing you just said makes any sense to me.

    The Tablet is Not Currently in Use.

    You've been talking about the wired network, but the tablets that are having issues aren't even connected to it.

    There's one tablet. the rest are Terminals hard wired just like a Desktop/laptop would be.



  • @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    I have to ask the dumb question. How are tablets being connected to a wired network?

    Access point on the firewall routed to the wired network.

    FFS, there is the issue.

    I know you normally have a network dedicated to POS. That doesn't magically free up availability for the wifi network when things get busy. The wireless environment is probably clogged full when the place gets busy. That'll be your bottleneck.

    FFS explain what you mean? Nothing you just said makes any sense to me.

    The Tablet is Not Currently in Use.

    You've been talking about the wired network, but the tablets that are having issues aren't even connected to it.

    There's one tablet. the rest are Terminals hard wired just like a Desktop/laptop would be.

    Does that matter?
    I guess i'm confused how One tablet communicating to the Network would cause the bottle neck..



  • @WrCombs said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    I have to ask the dumb question. How are tablets being connected to a wired network?

    Access point on the firewall routed to the wired network.

    FFS, there is the issue.

    I know you normally have a network dedicated to POS. That doesn't magically free up availability for the wifi network when things get busy. The wireless environment is probably clogged full when the place gets busy. That'll be your bottleneck.

    FFS explain what you mean? Nothing you just said makes any sense to me.

    The Tablet is Not Currently in Use.

    You've been talking about the wired network, but the tablets that are having issues aren't even connected to it.

    There's one tablet. the rest are Terminals hard wired just like a Desktop/laptop would be.

    Does that matter?
    I guess i'm confused how One tablet communicating to the Network would cause the bottle neck..

    No. I'm agreeing with Scott that it is probably a server issue. They're all writing to one place. Start there.



  • @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    I have to ask the dumb question. How are tablets being connected to a wired network?

    Access point on the firewall routed to the wired network.

    FFS, there is the issue.

    I know you normally have a network dedicated to POS. That doesn't magically free up availability for the wifi network when things get busy. The wireless environment is probably clogged full when the place gets busy. That'll be your bottleneck.

    FFS explain what you mean? Nothing you just said makes any sense to me.

    The Tablet is Not Currently in Use.

    You've been talking about the wired network, but the tablets that are having issues aren't even connected to it.

    There's one tablet. the rest are Terminals hard wired just like a Desktop/laptop would be.

    Whether it is 1, or 100, that it has the issue, but isn't talking to the network, tells you that the network isn't the common shared component that by failing would cause the problem.



  • @scottalanmiller said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    I have to ask the dumb question. How are tablets being connected to a wired network?

    Access point on the firewall routed to the wired network.

    FFS, there is the issue.

    I know you normally have a network dedicated to POS. That doesn't magically free up availability for the wifi network when things get busy. The wireless environment is probably clogged full when the place gets busy. That'll be your bottleneck.

    FFS explain what you mean? Nothing you just said makes any sense to me.

    The Tablet is Not Currently in Use.

    You've been talking about the wired network, but the tablets that are having issues aren't even connected to it.

    There's one tablet. the rest are Terminals hard wired just like a Desktop/laptop would be.

    Whether it is 1, or 100, that it has the issue, but isn't talking to the network, tells you that the network isn't the common shared component that by failing would cause the problem.

    Are you saying that it's not the tablet on a wireless network being routed?

    Blame it on not having enough coffee today, but I'm just not following.



  • @WrCombs said in Collision Domain - In POS:

    @scottalanmiller said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    I have to ask the dumb question. How are tablets being connected to a wired network?

    Access point on the firewall routed to the wired network.

    FFS, there is the issue.

    I know you normally have a network dedicated to POS. That doesn't magically free up availability for the wifi network when things get busy. The wireless environment is probably clogged full when the place gets busy. That'll be your bottleneck.

    FFS explain what you mean? Nothing you just said makes any sense to me.

    The Tablet is Not Currently in Use.

    You've been talking about the wired network, but the tablets that are having issues aren't even connected to it.

    There's one tablet. the rest are Terminals hard wired just like a Desktop/laptop would be.

    Whether it is 1, or 100, that it has the issue, but isn't talking to the network, tells you that the network isn't the common shared component that by failing would cause the problem.

    Are you saying that it's not the tablet on a wireless network being routed?

    Blame it on not having enough coffee today, but I'm just not following.

    The tablet doesn't share the bottleneck locations as well as not being routed.



  • @scottalanmiller said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @scottalanmiller said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    I have to ask the dumb question. How are tablets being connected to a wired network?

    Access point on the firewall routed to the wired network.

    FFS, there is the issue.

    I know you normally have a network dedicated to POS. That doesn't magically free up availability for the wifi network when things get busy. The wireless environment is probably clogged full when the place gets busy. That'll be your bottleneck.

    FFS explain what you mean? Nothing you just said makes any sense to me.

    The Tablet is Not Currently in Use.

    You've been talking about the wired network, but the tablets that are having issues aren't even connected to it.

    There's one tablet. the rest are Terminals hard wired just like a Desktop/laptop would be.

    Whether it is 1, or 100, that it has the issue, but isn't talking to the network, tells you that the network isn't the common shared component that by failing would cause the problem.

    Are you saying that it's not the tablet on a wireless network being routed?

    Blame it on not having enough coffee today, but I'm just not following.

    The tablet doesn't share the bottleneck locations as well as not being routed.

    But it is routed..



  • wouldn't it be?

    All terminals/Server are on the same ethernet network and have access to the internet (in this site setup) and the Access point is routed to the network that the terminals and servers are on , just plugged into a different port, and also has an internet connection. So.. it would be routed ? or am I just not understanding ?



  • @WrCombs said in Collision Domain - In POS:

    @scottalanmiller said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @scottalanmiller said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    I have to ask the dumb question. How are tablets being connected to a wired network?

    Access point on the firewall routed to the wired network.

    FFS, there is the issue.

    I know you normally have a network dedicated to POS. That doesn't magically free up availability for the wifi network when things get busy. The wireless environment is probably clogged full when the place gets busy. That'll be your bottleneck.

    FFS explain what you mean? Nothing you just said makes any sense to me.

    The Tablet is Not Currently in Use.

    You've been talking about the wired network, but the tablets that are having issues aren't even connected to it.

    There's one tablet. the rest are Terminals hard wired just like a Desktop/laptop would be.

    Whether it is 1, or 100, that it has the issue, but isn't talking to the network, tells you that the network isn't the common shared component that by failing would cause the problem.

    Are you saying that it's not the tablet on a wireless network being routed?

    Blame it on not having enough coffee today, but I'm just not following.

    The tablet doesn't share the bottleneck locations as well as not being routed.

    But it is routed..

    Not in your network diagram, it isn't.



  • @WrCombs said in Collision Domain - In POS:

    wouldn't it be?

    All terminals/Server are on the same ethernet network and have access to the internet (in this site setup) and the Access point is routed to the network that the terminals and servers are on , just plugged into a different port, and also has an internet connection. So.. it would be routed ? or am I just not understanding ?

    Am I missing something, is there more to the network, there is a router between the wifi and the server? There can be, but that would be really weird. But certainly can be.



  • @scottalanmiller said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @scottalanmiller said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @scottalanmiller said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @travisdh1 said in Collision Domain - In POS:

    I have to ask the dumb question. How are tablets being connected to a wired network?

    Access point on the firewall routed to the wired network.

    FFS, there is the issue.

    I know you normally have a network dedicated to POS. That doesn't magically free up availability for the wifi network when things get busy. The wireless environment is probably clogged full when the place gets busy. That'll be your bottleneck.

    FFS explain what you mean? Nothing you just said makes any sense to me.

    The Tablet is Not Currently in Use.

    You've been talking about the wired network, but the tablets that are having issues aren't even connected to it.

    There's one tablet. the rest are Terminals hard wired just like a Desktop/laptop would be.

    Whether it is 1, or 100, that it has the issue, but isn't talking to the network, tells you that the network isn't the common shared component that by failing would cause the problem.

    Are you saying that it's not the tablet on a wireless network being routed?

    Blame it on not having enough coffee today, but I'm just not following.

    The tablet doesn't share the bottleneck locations as well as not being routed.

    But it is routed..

    Not in your network diagram, it isn't.

    I left out the access point and tablet cause I didn't think it mattered. The tablet sits in the office until they have an event.



  • @scottalanmiller said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    wouldn't it be?

    All terminals/Server are on the same ethernet network and have access to the internet (in this site setup) and the Access point is routed to the network that the terminals and servers are on , just plugged into a different port, and also has an internet connection. So.. it would be routed ? or am I just not understanding ?

    Am I missing something, is there more to the network, there is a router between the wifi and the server? There can be, but that would be really weird. But certainly can be.

    what?

    no, it's the fireall with a route put in by the Firewall management company (not us) to have the access point for the tablet connect to the same wired network .



  • @WrCombs said in Collision Domain - In POS:

    @scottalanmiller said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    wouldn't it be?

    All terminals/Server are on the same ethernet network and have access to the internet (in this site setup) and the Access point is routed to the network that the terminals and servers are on , just plugged into a different port, and also has an internet connection. So.. it would be routed ? or am I just not understanding ?

    Am I missing something, is there more to the network, there is a router between the wifi and the server? There can be, but that would be really weird. But certainly can be.

    what?

    no, it's the fireall with a route put in by the Firewall management company (not us) to have the access point for the tablet connect to the same wired network .

    firewall = router. The terms have been synonymous for decades. So okay, it's routed, but outside of the network diagram.

    That seems like a big waste to expose the server anyway.



  • It sounds like this network is unlike your previously discussed networks -

    Do all devices have direct access to the internet?

    Is there Guest Wifi access for customers at this location?



  • @stacksofplates said in Collision Domain - In POS:

    @scottalanmiller said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @scottalanmiller said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    @scottalanmiller said in Collision Domain - In POS:

    @WrCombs said in Collision Domain - In POS:

    So it's not a collision Domain because their Obsolete in wired networks due to switches -

    I'm not sure what else could be causing the issue other than bad cabling/ Bad terminals/ Bad switches.
    May be worth replacing the other bar switch and changing out the Cabling under the bar.

    So start with the basics and see what you can track down. If you are getting congestion or bad switches / cabling, you'd expect to see it even with a ping. Ping from device to device and see if you ever get latency or drops. If not, likely it's not a networking thing.

    Can you describe the freezing? Like if you do X which devices freeze. And if you do Y, these other devices freeze.

    Only information I have is " when we're Busy, and we try to order items on the terminals they run slow and freeze up. then it comes back then it shows up. the delay is anywhere from 15 seconds to 2 minutes"
    Nothing specific when it comes to what their doing on the terminals.

    Any reason that there is a network suspicion then, why not suspect the server?

    Cause it's the exact same image/setup as the other site they have, and the other site doesn't run slow what so ever.

    Still, many times more likely to be a hard drive or something.

    This. Something like that trans.log is being written to a single 5400 RPM drive.

    This is one of the first things I was thinking - super slow (possibly dieing) HDD. and even if it's new, doesn't mean it could be bad from the factory.

    I agree with scott this seems much less like a network issue, and more like a server issue (wither it's hardware or software, we don't have enough information yet).

    Setup a continuous ping from several of the PCs, check them when the staff complain about the application hanging, see if the pings hang too.

    might be worth turning on performance monitoring and have it monitor the HDD/RAM/CPU



  • @WrCombs Everything in the same network is being switched no matter if its wireless or wired. In order to route, you need to move the packets to a different network.


Log in to reply