Results 21 to 25 of 25
Have you been able to ssh to the other computer yet? I would make sure that it works before dealing with an outside application such as putty. I'm not saying ...
- 01-15-2010 #21Just Joined!
- Join Date
- Jan 2010
- Posts
- 35
Have you been able to ssh to the other computer yet? I would make sure that it works before dealing with an outside application such as putty. I'm not saying putty is a bad piece of software; it's just that I would try to eliminate as many outside influences first.
- 01-15-2010 #22Just Joined!
- Join Date
- Dec 2009
- Posts
- 33
No, I have not been able to ssh from the other pc to the Fedora box. Both pcs are using putty to do it. I keep checking from the other pc also. I do understand what you are saying though and have noted it.
Any other ideas as what could be blocking putty from any pc to the Fedora box?
- 01-15-2010 #23
All you posts talk about trying to get into the box. Have you logged onto the box and tried to get out to anything? Maybe your connection is just not setup properly?
- 01-15-2010 #24Just Joined!
- Join Date
- Dec 2009
- Posts
- 33
Ya, that was a good thought. I was not able to ping anything from the Fedora box. I could browse the internet a few minutes ago.
So, I went back in and tried the internet and could not browse. I restarted the machine and then I could ping out from Fedora. Also, I could putty in from my machine. This makes no sense why sometimes I have connection to the network and sometimes I do not. But, thanks for the idea. Sometimes we get streamlined and forget the simple stuff.
- 02-11-2010 #25Just Joined!
- Join Date
- Dec 2009
- Posts
- 33
This whole issue had nothing to do with putty. My network would not be connected every time I started up my Linux box. I think it is because it is bridged. I have found in a few places that when the NIC is set to bridged in VMWare, that ip conflicts can arise.
Now, with that being said, if I restart my NIC card ( System -> Administration -> Network Device Control -> Deactivate and then reactivate ), then I can sometimes get to the internet. This does not work every time. Also, sometimes I can just restart Fedora and that will solve it. All I keep doing is restarting something and then eventually, usually within 2 or 3 restarts I can get the internet. At that point, I can user putty to connect to my box.
The whole point was to connect remotely in order to set do a mysql dump of a db onto this machine. After the network was cleared, it turned out that I was running the command correctly to set up the user's permissions using mysql. I set up a user to have permission for remote access so that the database could be copied over.
mysql> grant all privileges on <database name here>.* to 'username'@'localhost' identified by 'password'
A side note, I also found that you can restart the VMWare DHCP service in windows outside of the VWMare. This may help in some way with an ip conflict inside of the VMWare.
Hopefully this helps someone.
By the way, the point of this post was to say that unless you know exactly what is not allowing you to connect remotely, check if you have an internet connection. If not, restart the Fedora OS, restart the NIC card using the Network configuration, or restart the VMWare DCHP service in windows ( assuming you are runninng windows ) a few times until you get the internet on your OS.


Reply With Quote