can ping but cannot telnet (about VirtualBox)

My situation is:
I install the guest OS WindowsXp on host OS Debian via VirtualBox.
I try to use bridge-connecting to create the network.Thus,the guest
and host are in the network:10.0.1.1/24,and the host and other
computers are in the network:192.168.1.1/24.My host have two ip:
10.0.1.1 and 192.168.1.100.The ip of my guest is 10.0.1.2.
My problem is:
My guest can ping any ip which is activity,for example,it can ping
www.google.com and 192.168.1.102.But it cann't access any ip via a
tcp
connection.For example,after I telnet ptt.cc,the terminal turn black
and wait something and it shows that it has found the host.As the
same,I cannot access www.google.com via browser,my explorer also
shows
that it has found the host but waiting.
What should I do?
Thanks for any reply.
hoo

On Feb 1, 5:11*pm, Archmage <hoo.s...@gmail.com> wrote:
> My situation is:
> I install the guest OS WindowsXp on host OS Debian via VirtualBox.
> I try to use bridge-connecting to create the network.Thus,the guest
> and host are in the network:10.0.1.1/24,and the host and other
> computers are in the network:192.168.1.1/24.My host have two ip:
> 10.0.1.1 and 192.168.1.100.The ip of my guest is 10.0.1.2.

How is the router for the 192.168.1.0/24 LAN supposed to know that
packets bound for 10.0.1.2 go to the host? You have to do one of three
things:

1) Bridge the guest to the network interface in the 192.168.1.0/24
network and assign it an IP address in that range. Then it will work
the same way the host does, as a separate device on the LAN.

2) Assign the guest an IP address in a private network with the host,
and configure the host to NAT for the guest. Then it will work because
the host works and all connections will appear to come from the host.

3) Assign the guest an IP address in a private network with the host,
configure some other device to NAT for the guest, and configure that
device to route all packets on the private network to the host.

The short version of why this isn't working -- when this machine,
10.0.1.2 tries to reach a public IP address, what device rewrites the
packets to a legal source address? The host doesn't (or at least, if
it does, you haven't explained how), and the router for the
192.168.1.0/24 LAN doesn't (because it isn't configured to).

So the real question is not why doesn't it work, but why would you
expect it to work?

DS