Christian Ritter wrote:
> Dear colinuxers,
>
> I just installed colinux 1.7.1 under Vista on a brand new laptop. 'Went
> almost like butter: slirp interface allowed connections to the outside,
> tap interface to the windows OS on the laptop. However, frequently,
> after about 10 minutes, the slirp connection dies (at least attempts of
> reaching the outside via ssh requests or apt-get / I'm using a Debian
> setup). On the other hand, established connections via ssh remain
> operational.
>
> Here is the information of the setup:
> laptop connected to network via router modem (DSL)
> laptop runs Vista, Comodo, Antivir (and, obviously colinux)
>
> Today, I'll check over a different network entry point.
>
> Any ideas what I could check to see what happens to the slirp when it
> 'falls asleep'? so far I have not been able to get it back working
> without halting colinux and restarting it.
Use ProcessExplorer (or taskman) to see the current command line of
slirp after startup. kill the task colinux-slirp-net-daemon.exe and
start it again on new command prompt with the same parameters, you seen
before.
If the error comes again, view messages from this. Any errors from this
daemon there? I hope. This would help to find out the problem.
CTRL-C the colinux-slirp-net-daemon.exe and start it again. Helps this?
True, this is an ugly workarrount to not reboot coLinux completely.
Other idea: An DNS problem?
Try wget of a website you know from within coLinux with dotted
ipaddress. The ipaddress will see with "ping www.google.com" on windows
before.
Check the DNS on your windows side "ipconfig.exe /ALL" before and after
the stopping. Are there different?
Have more as one DSN there? Try to add the second and third DNS from
windows side to /etc/resolv.conf
How many "connected" networks you have on the windows side?
Remember: Slirp has no ping support. But, can you get some from your
router, perhaps a webconfig or start page with "wget ip.of.your.router",
or from other computers on your network?
--
Henry N.
|
