Hi all,

I just installed a fresh copy of Centos 7 on a new server that I built. When trying to connect to the server via my Mac's terminal nothing happens. What I mean is it is not communicating with it and will just time out.

I tried using the static IP that I setup during the installation. EX: ssh root@111.11.111.111

Of course the 1's are replaced with my static IP.

During the installation I used all 3 of my ssd's as the installation source. I chose the web/host option so I can use this as a web server. After reboot I see a black screen on my server monitor. I'm assuming that is normal behavior.

What must I do to connect remotely to finish configuring my we server. I also setup a custom host. Lets say I own thisismydomain.com. I used server847@thisismydomain.com. What exactly should I to do at my registrar to make this sub domain work?

Just point the sub domain to the static IP? I would rather create some sort of public IP I'm thinking for better security right? I'm also assuming I have to connect to the server to do this.

Update
I tried pinging this static IP and get:
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4

I'm using another static IP on my router. Do I need to somehow configure the new static IP for the server in the router somewhere also?

Did you install a desktop? You should see something when the computer was rebooted. If no desktop there should be a login in prompt but there is an idle timeout and it will go black. Any key press will turn the video back on.

Are you connected to the correct ethernet port? Is the static IP address 111.11.111.111 public or private. Private IP addresses like 192.168.0.1 are not routable, are used by everyone and pose no security risk if posted.

public or private? Centos/Redhat enables ssh and root access by default so it should work automatically if the network was configured correctly.

Thanks for the reply! I did not install any graphics cards as I plan to use for just a server. The MOBO does have factory on board graphics which I used to connect my monitor to. After reboot no matter what key I hit it is just a black screen. I'm thinking I need to reserver the STATIC IP in my router but I need to locate my Mac Address in order to do so but with the black screen and no login or command prompt in sight I am having difficulty doing so.

I can however get to the grub command line by hitting e during bootup but not sure I can do anything with that?

Which ISO did you use to install the system. DVD ISO, Everything ISO or Minimal ISO

Did you install a desktop?

After Grub defaults or you select the boot options all you see is a black screen not even a cursor? The boot messages are turn off by default. Although they are scrolling fairly fast if your system is hanging then it might provide some information. Pressing e enters edit mode and you can change the boot parameters but will not be saved.

Remove rhgb quiet from the kernel line
Press ctrl-x to start

I used the Desktop ISO version. I just noticed that the command prompt comes up after about 15-20 minutes. Not sure why it takes so long.

It should not take that long. Hopefully you can login remotely using ssh.

The command to see the network configuration is
ip a

I finally figured out what was wrong with my connection. Apparently you have to enable the network adapter inside of linux. Once I did that I was able to perform a yum update.

The biggest issue that remains is the boot time for the terminal to appear. It took 11 minutes for the terminal to appear after a safe shutdown.

I have 3 SSD’s installed. 1 on the Marvell SATA III controller and 2 on the Intell Sata III controllers which use 6/GB’s of transfer. During the Centos install it asked which disk to install Linux on. I chose all 3.

Any idea as to why it takes 11 minutes to show? Anything in my MOBO settings I should be aware of?

https://www.newegg.com/Product/Produ...82E16813157350

Thanks!

To see where the system could be stalling run the following command. It will show how long it takes for each service to start which hopefully points you in the right direction.

systemd-analyze blame

Thanks! Everything looks good there I think.

Everything loded in milliseconds except for the following:

24.832s kdump.service
6.082s network.service
1.678s lvm2-pvscan@8:2.service