Jump to content

DJRon

Members
  • Posts

    61
  • Joined

  • Last visited

Everything posted by DJRon

  1. Even if I physically disconnect or shutdown the server, other computers on the network still have issues accessing the WebGui. Server still has to be manually shutdown and rebooted. It happens whether I am hard wired with an Ethernet cable or attempting to connect wireless. The details for the offending laptop are: OS: Windows 8.1 64 bit Processor: Intel® Core i7-4700HQ CPU @ 2.4GHz Memory: 12.0 GB System Type: 64 bit Operating System, x64 based processor Network Adaptors: Qualcomm Atheros AR8171/8175 PCI-E Gigabit Ethernet Controller (NDIS 6.30) Broadcom 802.11ac Network Adaptor
  2. Thanks for suggesting. I meant to include that in my original post. I did try accessing through both Chrome and IE.
  3. All machines on my network can access the media storage with no issues. I have a laptop (my primary) on my network, that causes an issue when accessing webgui from it. All other computers on the network can access the WebGui with no issue, until I attempt to access from the specific laptop. Once this specific computer accesses the main page on the WebGui all the other computers on the network can still access the shared storage; but none of them can access the WebGui page again until a telnet session is used to bring down the array and restart the machine. I have tried disabling the anti-virus (BitDefender 2015) on this specific laptop, but the issue remains. I am open to any suggestions. My next step is to identify network related processes and shut them down one at a time until I find the culprit. Any other ideas, and suggestions are welcome. I have attached a list of running processes on the laptop causing the issue. Thanks for your input. processlist.txt
  4. I am still seeing very slow WEBUI response times. I have included the latest syslog and included additional troubleshooting attempts. - Moved the box directly near the router, (bypassed gig switch) and plugged directly into router with a known good cable. - Installed a new Intel NIC card (Intel PWLA8391GTLBLK PRO/1000 GT Desktop Network Adapter) - Disabled the onboard NIC I can read and write to the Raid fine, just slow response from the WebUI. Sometimes it responds instantly on the first click of a menu option, sometimes it takes up to 5 minutes, still other times if I click the Menu option 3 - 4 times in rapid succession, it responds instantly. Any new ides or options would be appreciated. Thanks. SYSLOG_20150102.txt
  5. Thanks for taking the time to look at the log. I cannot event get the WebUI to respond now, so I have no way of knowing what is going on unless I tail the log through a telnet session. I have tried different browsers, different machines, with different antivirus, transfer speeds to and from the machine are good (except during the parity check). I am going to look into settings on my router today and hope to find something. Other ideas are most certainly welcome. Thanks and Merry Christmas.
  6. Thanks to everyone who has looked at this and can offer input. I have attached the latest syslog. I had to pull from a telnet session. Thanks for your time and input. syslog_out.txt
  7. I think it is a latency issue with the WEBUI. I can acces through telnet without issue and even transfer files with good speed. I will work on pulling the syslog through telnet and post.
  8. Thanks for the reply. I have now assigned it a static IP Address and checked to make sure no other machines are using that name. The first time I switch to a new screen in the WebUI it is fast, but then very slow from the second selection on.
  9. I have looked in the forums and was not able to locate information that resolved my issue. I just did the install yesterday and the WebUI has been very slow from the start.. sometimes up to 5 minutes or more just to move to another page. My SysLog is attached and my configuration should be in my profile. Thanks in advance for any assistance. SMB is set to Workgroup (Workgroup name matching computer trying to access from) I have tried the following: - Different Network Cables - Accessing Through Different Browser - Accessing Through Different PC Log_20141222a.txt
×
×
  • Create New...