Ken Perl wrote:
> I configured slirp network that works fine before, but today maybe our
> company's network is changed but I'm not sure what is changed. now I
> can not connect to other machines within our company anymore, I can
> before.
>
> the colinux(debian) ip is 10.0.2.15, the netstat -r output says the
> default route is 10.0.2.2, the dns namserver is 10.0.2.3, I can ping
> the route 10.0.2.2, and I can ping the 200.10.2.83 but can't ping its
> hostname. ping from my XP to the hostname is ok.
>
> any idea what's wrong with the nameserver 10.0.2.3?
>
Inside coLinux check the DNS configuration with
host -v name
This give informations what your gets from dns sever for the host with
'name'.
10.0.2.3 is mapped inside slirp to the first dns server from your
windows side. Perhaps you have more dns servers and the first is not
usable? In this case, setup the second dns server from windows (ipconfig
/all) also as secondary dns inside your coLinux, by adding it to
/etc/resolve.conf.
PS: Ping from coLinux Slirp to outside is not supported for all hosts.
You can ping to the router 10.0.2.2 alltimes. To other hosts only, if
thre runs an UDP ECHO server (port 7/udp).
--
Henry
|
