Unable to SSH or HTTP after Installation

[tligon]

OK so I took a perfectly clean new Fedora 1 core with webmin installed and did what appeared to have been a successful installation of DSM (said to restart to reload fstab changes) once I did that I can no longer login using SSH shows login but once you enter a name the session closes? When you try http: to the ip address you get nada nothing zip..

I did not receive the lic file yet but figured at least ssh should still work?

What am I missing. Lic ordered Sat.. no emails yet.

[LeeJ]

I would venture to say that sshd was not set to startup as dsm does not bother sshd at all during the installation process. In terms of the license I will check as to why you have not received your information. Did you order a monthly or one time license?

[LeeJ]

put in a support request containing the information for your machine and we will take a look.

[tligon]

I orderd a monthly lic. where do I open the support request at?

Before the installation sshd was running and is set to start on reboot. Double checked and tripple checked. When you port scan it shows it running.. but input ANY username and the putty session just closes.

Thanks

[LeeJ]

The support email addres is support <at> zervex.com.

I would put a console on the box as that behavior does not sound right. Take a look at the installer it is a shell script. It does not touch sshd or anything that would cause a problem like the one you are describing it only installs rpms using yum.

Once you are able to gain access to the machine send us the machine info and we will take a look at as to why apache isn't running.

Another thing to check is iptables. Make sure you don't have the default ruleset or something similar.

Also, send a message to billing <at> zervex.com inquiring about the license. If the order fails web validation it is manually processed. Someone will be coming in to do manual order processing in about an hour from now.

[LeeJ]

Problem resolved via support request.
Response from client:

The problem was that the IP was on another machine! When they finally
figured it out!.. Took till this afternoon... everything worked fine until
the box was rebooted!
Anyway it appears that all is well now.