Apfelbomber Posted June 2, 2020 Share #1 Posted June 2, 2020 I recently updated my Microserver Gen8 which is running on Jun´s loader v1.03b as a 3615xs to DSM version 6.2.3-25426 (it was running on 6.2.3-25426 before, with the only issue being that I couldn´t shut it down or restart it via DSM) and since that update, the server can´t connect to any services. The package center is unavailable, as are Plex and TeamViewer. I can access the Server just fine, as long as I´m within the network. There´s no data loss and no other issues so far. It´s not a router problem either, the settings there are the same as always and I don´t see anything that could cause this problem. I´m using an Intel NIC because the onboard ports wouldn´t be recognized by DSM after update 6.2.3. However, after the latest update, the onboard ports were visible again in DSM. Using these ports instead of the ports on the NIC doesn´t resolve the issue either. I changed the serial number of the loader because I had another Gen8 with the same settings in the network. I don´t have that one anymore. I also listed all four mac addresses in the loader, just in case they started working again after another update (which they obviously did), but maybe the four ports may cause the issue too, so I´ll try to remove the NIC and boot again, just to see if anything changes. If there´s any Gen8 user out there who has it working on 6.2.3-25426 I´d really appreciate any help whatsoever. The specs of my Gen8 are the following: 12Gigs of HP ECC RAM Intel Xeon E3 1230 Intel 2-Slot 1Gbit NIC Many thanks in advance! Quote Link to comment Share on other sites More sharing options...
Apfelbomber Posted June 2, 2020 Author Share #2 Posted June 2, 2020 Update: Disabling the Intel NIC seems to have resolved the problem. Maybe the four ports were too many? Quote Link to comment Share on other sites More sharing options...
Apfelbomber Posted June 2, 2020 Author Share #3 Posted June 2, 2020 Update: Or not. Sporadically, the package manager has a connection, but it seems to be completely random and unpredictable. Quote Link to comment Share on other sites More sharing options...
Balrog Posted June 4, 2020 Share #4 Posted June 4, 2020 The first thing coming to my mind during reading your text is: "check speed and duplex settings!". Sometimes there is a mismatch between the NIC and the connected network switch regarding these settings which results exactly into the issues you are describing.The default setting in DSM is "auto" but maybe it helps if you to set speed/duplex fix to "1000mbit/full duplex". You can find the setting in the NIC settings of DSM.Before testing this I would suggest that you configure the second NIC as a fallback with a own fixed IP if the change doesn't work and you lost completely your connection.You can also check your network switch (if your have a manageable one) and check if the speed/duplex settings from this side is matching what DSM sees and set them fix to 1000 mbit/full duplex. 1 Quote Link to comment Share on other sites More sharing options...
Apfelbomber Posted June 4, 2020 Author Share #5 Posted June 4, 2020 The issue was resolved thanks to another post in the Updates section - I simply had to delete the DNS entry and re-enter it. That fixed it. 5 hours ago, Balrog said: The first thing coming to my mind during reading your text is: "check speed and duplex settings!". Sometimes there is a mismatch between the NIC and the connected network switch regarding these settings which results exactly into the issues you are describing. The default setting in DSM is "auto" but maybe it helps if you to set speed/duplex fix to "1000mbit/full duplex". You can find the setting in the NIC settings of DSM. Before testing this I would suggest that you configure the second NIC as a fallback with a own fixed IP if the change doesn't work and you lost completely your connection. You can also check your network switch (if your have a manageable one) and check if the speed/duplex settings from this side is matching what DSM sees and set them fix to 1000 mbit/full duplex. Many thanks anyways! Quote Link to comment Share on other sites More sharing options...
Balrog Posted June 5, 2020 Share #6 Posted June 5, 2020 Nice to read that you solved the issue. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.