Search the Community

Showing results for tags 'networking problem'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Information
    • Readers News & Rumours
    • Information and Feedback
    • The Noob Lounge
  • XPEnology Project
    • F.A.Q - START HERE
    • Loader Releases & Extras
    • DSM Updates Reporting
    • Developer Discussion Room
    • Tutorials and Guides
    • DSM Installation
    • DSM Post-Installation
    • Packages & DSM Features
    • General Questions
    • Hardware Modding
    • Software Modding
    • Miscellaneous
  • International
    • РУССКИЙ
    • FRANÇAIS
    • GERMAN
    • SPANISH
    • ITALIAN
    • KOREAN
    • CHINESE
    • HUNGARIAN

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 5 results

  1. 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!
  2. All, Thanks for any input. I moved house, new router with new base IP. While at old house XPenolgy sever had manual IP and admin account disabled. New house, I boot server and see in Synology Assistant old IP address and Connection Failed, I select option to Setup to allow "wizard" to configure network. It asks for Admin PW. no matter what I input for PW it fails. I am (clearly) not an Network SME Cheers MF
  3. Hello friends, I have a problem with the network connection. The connection is lost sometimes during the day, especially when there is intensive use of network traffic, although it also happens sometimes when nothing is used. I have DSM 6.2.1-23824 Update 6 installed with jun's boot 1.04b, DS918 + on a Gigabyte GB-BLPD-5005 nuc (http://en.gigabyte.com/products/page/desktop_platform/gb-blpd-5005rev_10). It uses the Realtek RTL8111HS NIC. As I mentioned, the network connection is lost both in local and external network for a few seconds or minutes, and the Log Center shows the network loss as "[LAN 1] Link down" and "[LAN 1] Link up". Any idea why this problem can occur? I have verified that it is a DSM problem, since only the connection in DSM is lost and the network card does not give problems with a Linux distribution. I have also tried different routers, ports and cables for the network, getting the same result. Should I try some extra.izma to check if it is fixed? Thanks in advance and sorry if I do not express myself correctly in anything, my English is not very good and I have used a translator for some parts of the text.
  4. Hi, I followed the instructions and prepared my USB STICK and bootet successfully. Wether find.synology.com nor the synology assistant finds the machine. It uses the intel I219-LM NIC which is in the supported NIC's list but it is just not found. I bootet the machine with another stick win10PE to test if the NIC is working and it is working. Some Data to the NIC : VEN_8086&DEV_15B7&CC_0200 Any Ideas? rgds 0ni
  5. Hello, I tried to install DSM 6.x with bootloader ver. 1.02b on virtualbox. Everything went fine but only on one compuer. I have those problems: 1. I created a virtual xpenology on my laptop (Lenovo, network card Realtec), booted it, it was found by synology assistant. But when I exported the virtual appliance (I wanted to use it on another computer) and imported it on another computer, the nework didn't work at all. I booted bootloader without problem, but could not find it by synology assistant. It seems to me, that there is a problem with networking. I compared virtualbox setting on my laptop with virtualbox setting on the computer - they were the same. I tried to create a virtual machine from scratch on the computer - networking didn't work (it was not found). I tried the same procedure on another two computers and it was the same result. I don't understand why it works on my laptop and don't work on another 3 computer with virtualbox. I did: - every virtual box are the latest versions - all computers are Windows 7 x64 - virtualbox extension pack is installed on all computers - antivirus was uninstalled - firewall disabled - I tried bootloader 1.02a , 1.02b, 1.01 the same result - intel virtualization technology in BIOS enabled - MAC addres in virtualbox set according the MAC found by synology assistant on my laptop - networking on virtualbox is set to "bridge" - linux type in virtualbox settings is "Linux 2.6 / 3.x / 4.x 64bit" . I tried Ubuntu 64bit, Linux 2.4 64bit nothig worked - I tried to change network card type in advanced network setting in virtualbox - the same result - the same result was with DMS for DS916 and DS3617xs 2. If I start bootloader, the message "Booting the kernel" appears. I found in this forum that it is correct behaviour. But if I used bootloader for DSM 5.2 it showed all booting process and it was possible to log into command line directly form virtualbox console. Is there any way how to do the same with bootloader for DSM 6.x? I would like to log in via command line from virtualbox console and check network settings and if the eth devices are up or down. Don't somebody know if someone is about releasing next (improved) version of xpenology bootloader or how to modify it that I could run command line after booting the kernel?