Results 1 to 5 of 5

Thread: connecting to headless server when new router installed

  1. #1
    Senior Member
    Join Date
    Aug 2005
    Location
    Hamilton
    Posts
    590
    Thanks
    20
    Thanked
    2 times in 2 posts

    connecting to headless server when new router installed

    Hi i have a whs setup(192.168.0.10) that used to connect on virgin superhub router (192.168.0.1) now moved to plusnet and new router has (192.168.1.254) address all the other pc's in the house connect okay except the whs.
    I have rebouted everything a few times but the whs still doesn't show on the network.

    Any help?

    Thanks

  2. #2
    Minister of Silly Walks
    Join Date
    Feb 2013
    Location
    Surrey
    Posts
    314
    Thanks
    35
    Thanked
    67 times in 54 posts
    • stilkun's system
      • Motherboard:
      • GigaByte GA-B75-D3V (rev 1.1)
      • CPU:
      • Intel® Core™ i5-3470 Processor
      • Memory:
      • Patriot Black Viper 24GB 1600 Mhz
      • Storage:
      • Crucial M500 240GB, Samsung 32 GB mSATA, MAXTOR SATAI 250 GB, WD Blue SATA III 1TB
      • Graphics card(s):
      • Sapphire HD 7850 OC edition 2 GB
      • PSU:
      • XFX 450w Core
      • Case:
      • AvP Triton Mid Tower PC Case
      • Operating System:
      • Windows 8.1 Pro Update 1 (64 Bit)
      • Internet:
      • 8 Mbps (1 MBps) Tiscali

    Re: connecting to headless server when new router installed

    Check your WHS if it is assigned with a static IP address. You will need to change the IP address if it is.

  3. #3
    Senior Member burble's Avatar
    Join Date
    May 2007
    Location
    Olney
    Posts
    1,138
    Thanks
    8
    Thanked
    90 times in 89 posts

    Re: connecting to headless server when new router installed

    You'll need to change the IP address of the WHS server to the 192.168.1.0/24 network. Alternatively you could change everything else to 192.168.0.0/24.

    As it's headless though you may need to temporarily change the IP address on one machine to the 192.168.0.0 network, say 192.168.0.100 for example then connect to the WHS server and change its IP address to something like 192.168.1.10. (check that you give it an address outside of the DHCP scope that's set on the Plusnet router).

    The other option is to change the LAN IP address on the Plusnet router to 192.168.0.1 then reboot it and it should give all the DHCP clients an IP address back in the 192.168.0.0/24 subnet and you'd then be able to connect to the WHS server.

  4. #4
    Senior Member
    Join Date
    Aug 2005
    Location
    Hamilton
    Posts
    590
    Thanks
    20
    Thanked
    2 times in 2 posts

    Re: connecting to headless server when new router installed

    I can't see the server on the network and have rebooted everything a few times, but if i replace the router with an unmanaged switch and reboot everything works fine, i have checked that assign an ip address automaticaly is ticked but still the same result, so any ideas?

    Thanks

  5. #5
    Anthropomorphic Personification shaithis's Avatar
    Join Date
    Apr 2004
    Location
    The Last Aerie
    Posts
    10,857
    Thanks
    645
    Thanked
    872 times in 736 posts
    • shaithis's system
      • Motherboard:
      • Asus P8Z77 WS
      • CPU:
      • i7 3770k @ 4.5GHz
      • Memory:
      • 32GB HyperX 1866
      • Storage:
      • Lots!
      • Graphics card(s):
      • Sapphire Fury X
      • PSU:
      • Corsair HX850
      • Case:
      • Corsair 600T (White)
      • Operating System:
      • Windows 10 x64
      • Monitor(s):
      • 2 x Dell 3007
      • Internet:
      • Zen 80Mb Fibre

    Re: connecting to headless server when new router installed

    Sounds like you are running a DHCP server on the WHS box on the 192.168.0.x subnet. Removing the router causes the DHCPs to stop clashing and you get the right IP.

    As soon as you add the router in with its 192.168.1.x subnet and DHCP server, things go nuts again.

    Add the switch, connect to the WHS box, disable the DHCP server on it and then update it's IP details to be on the 192.168.1.x subnet, then swap the router back in.

    Or if possible, add a static route on the router between 192.168.0.x and 192.168.1.x
    Main PC: Asus Rampage IV Extreme / 3960X@4.5GHz / Antec H1200 Pro / 32GB DDR3-1866 Quad Channel / Sapphire Fury X / Areca 1680 / 850W EVGA SuperNOVA Gold 2 / Corsair 600T / 2x Dell 3007 / 4 x 250GB SSD + 2 x 80GB SSD / 4 x 1TB HDD (RAID 10) / Windows 10 Pro, Yosemite & Ubuntu
    HTPC: AsRock Z77 Pro 4 / 3770K@4.2GHz / 24GB / GTX 1080 / SST-LC20 / Antec TP-550 / Hisense 65k5510 4K TV / HTC Vive / 2 x 240GB SSD + 12TB HDD Space / Race Seat / Logitech G29 / Win 10 Pro
    HTPC2: Asus AM1I-A / 5150 / 4GB / Corsair Force 3 240GB / Silverstone SST-ML05B + ST30SF / Samsung UE60H6200 TV / Windows 10 Pro
    Spare/Loaner: Gigabyte EX58-UD5 / i950 / 12GB / HD7870 / Corsair 300R / Silverpower 700W modular
    NAS 1: HP N40L / 12GB ECC RAM / 2 x 3TB Arrays || NAS 2: Dell PowerEdge T110 II / 24GB ECC RAM / 2 x 3TB Hybrid arrays || Network:Buffalo WZR-1166DHP w/DD-WRT + HP ProCurve 1800-24G
    Laptop: Dell Precision 5510 Printer: HP CP1515n || Phone: Huawei P30 || Other: Samsung Galaxy Tab 4 Pro 10.1 CM14 / Playstation 4 + G29 + 2TB Hybrid drive

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •