Find the answer to your Linux question:
Page 2 of 3 FirstFirst 1 2 3 LastLast
Results 11 to 20 of 25
I tried the service sshd start I got 'starting sshd: /var/empty/sshd must be owned by root and not group or world-writable'. I did an 'su root' and now have my ...
  1. #11
    Just Joined!
    Join Date
    Dec 2009
    Posts
    33
    I tried the service sshd start

    I got 'starting sshd: /var/empty/sshd must be owned by root and not group or world-writable'.

    I did an 'su root' and now have my prompt as
    root@pcName>

    Do I need to log in from the beginning as root in order to do the service sshd start command?

  2. #12
    Linux Engineer Kieren's Avatar
    Join Date
    Aug 2007
    Location
    England
    Posts
    845
    Yes sorry, you will need to be root to run that command
    Linux User #453176

  3. #13
    Just Joined!
    Join Date
    Dec 2009
    Posts
    33
    Ok, so I logged in as root. I ran the command

    I had to change permissions on sshd to 755. Then I was able to start sshd.

    root>services sshd start

    Now, I get a network timeout error when I try to putty in. I have the firewall disabled. I googled and found that it may be a firewall issue. Will VMWare set up a firewall? Maybe it is blocking something. Also, I have windows firewall turned off in windows xp. I am running the vm on the same pc I am using. I have symantec 11 running on windows xp also. I do not know what could be causing this so I am just listing anything I can think of. Are there other steps in Linux I need to take now? Do you know of any other possibilities considering what I have listed above?

  4. #14
    Linux Engineer Kieren's Avatar
    Join Date
    Aug 2007
    Location
    England
    Posts
    845
    Are you able to connect to the ssh server from the Fedora machine? By doing this first before trying to connect from Windows you don't need to worry about firewalls.

    Does the command:

    Code:
    /sbin/service sshd status
    Tell you that the sshd is now running?
    Linux User #453176

  5. #15
    Just Joined!
    Join Date
    Dec 2009
    Posts
    33
    I think I just connected.

    I did what you said.

    >ssh localhost

    "The authenticity of host 'localhost' (127.0.0.1)' can't be established. RSA key fingerprint is .......
    Are you sure you want to continue connecting (yes/no)?"
    I entered yes
    Warning: Permanently added 'localhost' (RSA) to the list of known hosts.
    root@localhost's password:
    I entered the password
    Last login: Thu Jan 14 15:48:52 2010

    Does that mean I logged in through ssh?

    I am still timing out in putty though

    the service sshd is started now.

  6. #16
    Linux Engineer Kieren's Avatar
    Join Date
    Aug 2007
    Location
    England
    Posts
    845
    Okay that means ssh is running. The fact that you can't connect through Putty probably means that you are either being blocked by a firewall or you are configuring Putty wrong (Maybe using the wrong IP address or something).
    Linux User #453176

  7. #17
    Just Joined!
    Join Date
    Dec 2009
    Posts
    33
    Ok

    Thanks. This is a lot further than I would have gotten on my own. I will try to see what is blocking it. Maybe I can do wireshark on my end in windows and the will show me something? Who knows, maybe I will get lucky.

    Thanks for your time. Maybe some others will learn from this in the future also. I always try to make it my goal to put as much information into forums now as I can in case someone else runs into the same issue.

    Wish me luck!

    I really enjoy this forum by the way. There are many helpful people on here.

  8. #18
    Linux Engineer Kieren's Avatar
    Join Date
    Aug 2007
    Location
    England
    Posts
    845
    That's okay. Wireshark would be a good way to go but make sure your settings in Putty are correct first as that will save you a lot of time
    Linux User #453176

  9. #19
    Just Joined!
    Join Date
    Dec 2009
    Posts
    33
    I turned on logging in putty. Here is what I saw in the log:

    =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2010.01.14 17:07:01 =~=~=~=~=~=~=~=~=~=~=~=
    Event Log: Appending session log (SSH raw data mode) to file: C:\Documents and Settings\Tim\Desktop\putty.log
    Event Log: Looking up host "192.168.1.201"
    Event Log: Connecting to 192.168.1.201 port 22
    Event Log: Failed to connect to 192.168.1.201: Network error: Connection timed out
    Event Log: Network error: Connection timed out

    I also ran wireshark. I have 3 interfaces I can choose from. I ran wireshark on the other interfaces 2 and there were zero entries. I am pretty sure this is expected since I chose 'bridged' in VMWare. On the first interface card, which is the bridged one, I cannot see traffic from putty. I am not exactly sure what I am looking for. I checked entries from my ip to several possible locations. Since I am using a bridged connection, do I check for the destination to still be my ip address? Or will this be some other ip address since the connection is bridged?

    Also, in putty, I put the ip of Fedora and port 22. Is this correct? Port 22 is the port you always use when trying to putty into another box, right?

  10. #20
    Just Joined!
    Join Date
    Dec 2009
    Posts
    33
    I used putty to connect to a different box that I have been able to connect to in the past. I connected. Now, I see protocol SSH in wireshark. So, does putty have to connect first in order for wireshark to capture traffic? Isn't there some type of request done first that would show up in the capture? Is there something different for Fedora? I was able to connect using the ssh localhost as posted above. I know this now has become more of a putty / wireshark issue wince I can connect with ssh localhost. Does anyone have any more ideas for putty and wireshark. I basically still need to find what is blocking putty. I do not need to use wireshark if there is another way to find out why I am being blocked.

Page 2 of 3 FirstFirst 1 2 3 LastLast

Posting Permissions

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