problem connecting from a xp host to guest ubuntu linux

[asifsehzaad]

I have installed ubuntu server on my virtual box, assigned 192.168.1.27 to it while installation, enabled the pae switch and am using the host interface (virtual box creates a software network adapter) and i have assigned a staic IP to that 192.168.1.27 now i am able to ping that adapter but not the ubuntu server because i can't telnet or ssh into it...

from inside the virtual machine... I am able to do a ssh to itself... so that means ssh daemon is also running well...

is there something that i am missing.

[TerryE]

You might need help but the chances of getting it are slim if you use such a meaningful title as "need help". That describes 95% of those that post topivs to this forum. Edit your first post and change the title to something meaningful.

OK so your VM guest server has a static IP address, but how have how configured your host? Is it NAT or bridged? Is it Linux, Windows or Mac? Have you read and followed the relevant parts of section 6 of the UG?

[Sasquatch]

Ok, nice setup. Host interface IP: 192.168.1.27, Server IP: 192.168.1.27. See anything strange? Yes, both computers have the same IP address, resulting in a conflict and no way of connecting to one or the other. Change the Host Interface OR the Guest Server to something different, like 192.168.1.28. Once you've done that, you can connect to the server.

Really, learn some basic networking before coming here wining it doesn't work. If you don't know what you're doing, nobody will know what you mean and how to solve your problem as you don't even know what the exact problem is.

[TerryE]

asifsehzaad, Sasquatch does make some valid points. Setting up networking is quite complicated and you do need to read up on it first. If you get it wrong then things don't work. If you use NAT and let the setting default, then outbound network from your VM will work out-of the-box but you need to use port mapping as I described in Please help: host to guest network connection trouble.

Setting up a bridged network is more complex and configuring this is different for Linux and Windows Hosts. You do need to read up carefully on this. This is one area that VMware is a lot more user friendly: you just click on the NAT/Bridged option and everything just works.

Sasquatch, the average user has a very superficial knowledge of IT and either doesn't have the time or the interest to read technical documentation. The VBox "user" guide is really a technical introduction to VBox's use; it uses technical terminology without explanation throughout. It was written by IT pros for IT pros. As is much of the Linux documentation. A real user user guide would be targeted at the actual typical user. In this case it should take the user through the basic use case variants (e.g. setting up a bridged Windows client on a Linux host) in simple steps with screen shots where the user tool is a GUI.

I think your criticism is harsh. If VBox is only interested in targeting people who have graduate training in IT or an equivalent hobby interest then it will only have a tiny audience. Most users today want to use a PC as a tool. They need virtualisation because they need to run multiple OSs and setups but don't see the need to buy the H/W or pay the additional bills. For VBox to be a top three product, then it must be friendly to this user community.

[Sasquatch]

Sasquatch, the average user has a very superficial knowledge of IT and either doesn't have the time or the interest to read technical documentation. The VBox "user" guide is really a technical introduction to VBox's use; it uses technical terminology without explanation throughout. It was written by IT pros for IT pros. As is much of the Linux documentation. A real user user guide would be targeted at the actual typical user. In this case it should take the user through the basic use case variants (e.g. setting up a bridged Windows client on a Linux host) in simple steps with screen shots where the user tool is a GUI.

I think your criticism is harsh. If VBox is only interested in targeting people who have graduate training in IT or an equivalent hobby interest then it will only have a tiny audience. Most users today want to use a PC as a tool. They need virtualisation because they need to run multiple OSs and setups but don't see the need to buy the H/W or pay the additional bills. For VBox to be a top three product, then it must be friendly to this user community.

Still, people who are new to the whole virtualisation scene should read more about how it works, what to do when it doesn't work and shouldn't hit the forums on the slightest set back.
As I can take from his post, he has some knowledge about things. He set up a host interface nicely (not that hard on Windows), but forgot to read more about network setup concerning IP addressing.
As you know too, this is not a really technical forum, so advising someone to read more before comming here is not a harsh critic, it's actually a really good advice. Why? Because not everyone here know about networking and how to troubleshoot it. And it is not a direct VB issue, just a misconfiguration.

[asifsehzaad]

I got that working as soon as i changed it to a different ip address... wow! that thing worked like a charm. Actually what i was thinking was that VirtualBox will be binding to that host adapter...but it is just your interface to the virtual box internal network (or if i am still not correct i would love to get a shove in the correct direction...) that solved my problem. thanks for this...

[asifsehzaad]

ok after reading the comments in details...hmmm... sasquatch has got a point there ... but i tried to find the info i could not lay my hands on that... may be i didn't try hard...but i did try it believe me... and i am a developer guy not a networking guy... and i also know that if you keep same ip address of two machines that some sort of error should be thrown out... which was never happening... so there was now way for me to figure that out... i never saw a ip conflict happening....

[asifsehzaad]

the above is the configuration now... and i am not able to ping the guest image... (earlier during the day I was able to connect from office network... when my lan's ip was not 192 range... but at home it is 192.168.*)... [/img]

[asifsehzaad]

As soon as i bring the virtual box host adapter to the bridge and try to do some pinging between the two macihines i get a BSOD (Blues screen of death)....which says there was something wrong with tcpip.sys (let me guess here virtualbox's driver giving problems....) after coming around.... i submitted the error report to microsoft...but the solution from the automated response was useless..

http://wer.microsoft.com/responses/Resp ... fd47e4caf8

so.. this really is becoming a problem now.... i would have to keep them on a separate network range then... i think that.

[TerryE]

asifsehzaad, if you want to include text listings just paste them into a

Code: Select all

 block.  It's far easier.  

Can I go back to your requirements for a bit.  You have an ubuntu server VM  running inside a Window (?XP?) host.[list][*]What version/SP of windows are you running[*]What version of VB[*]What outbound services do you want to present? HTTP, SSH? what?[*]What machines need to access those services? Is it only processes on the Host or is it your wider home LAN?[/list]For example, I have a LAMP Ubuntu JeOS config which I use as a test bed to develop forums like this one.  I only need NAT which makes configuration much simpler.  I map port VM:80 -> host:81; VM:22 -> host 2222 and this gives me all the connectivity that I need.  Don't play in the mud unless you have to!!

[asifsehzaad]

I gues i would stay off the mud... as that is not what i want...thanks for all the help extended.