Menu
▾
▴
Re: [coLinux-users] vista, samba and tuntap blocks
|
From: Frank <col...@fr...> - 2008-04-17 15:42:34
|
Hi David, thanks for your hints - but the problem still exists. - First I have deactivated the "Network discovery" : The Problem with the freeze still exists. - Then I've stopped and deactivated the SSDP Discovery Service and the UPNP Device Host Service : The Problem with the freeze still exists. I checked with wireshark - now the problem came up without the bunch of SSDP-Messages send to the coLinux - Next I've disabled the "auto tuning mode" of the "network window size" with "netsh int tcp set global autotuninglevel=disable" : The Problem with the freeze still exists. I checked the behavior after each change and again after a reboot before I say: still exists. None of the changes above solves the problem but I've left the features disabled and every next step was in addition. Your suggestion to downgrade to XP ist not that funny - my new notebook only supports windows vista. The only chance may be a switch to an other virtualisation software - hoping the problem disappears after that. But I love coLinux ;-) it's that uncomlicated! Frank > Hi Frank, > > I don't run Vista, but can't you simply delete, disable or uninstall the > "Universal PNP" service from the list of services loaded in the TAP > adapter's "Network Connection" properties on Vista (like you can on XP)? > > I completely uninstalled UPNP from: > > control-panel > /add-remove-programs > /add-remove-windows-components > /networking-services > > IMO, UPNP is just a big ginormous security hole anyway. What is it > supposed to do, allow Windows to tell your LAN's router to open ports in > the firewall for P2P file-sharing apps and "discoverable" printers? > Please... like anyone would trust a Windows driver to automatically > reconfigure their LAN's router... > > I'm not surprised UPNP is fire-storming your TAP adapter. But I'm running > Debian etch (on a recent colinux 0.8.0 snapshot too), I share files from > colinux's /home/* dirs with Windows quite extensively using Samba, I use > these shares heavily in my daily work from the Windows side with no > problems and have been doing so for a couple of years now (just to reassure > you that it *can* work). > > Maybe consider joining the rest of us in a warm, satisfying downgrade back > to XP? :-) > > -dave > > > ----- Original Message ----- > From: "Frank" <col...@fr...> > To: <col...@li...> > Sent: Wednesday, April 16, 2008 5:17 PM > Subject: [coLinux-users] vista, samba and tuntap blocks > > > >> Hello everybody, >> I have a strange behavior in setting up a tuntap connection between >> coLinux and the Windows Vista Host. First I have to say - IT WORKS >> INITIALLY - so it seems not to be one of the simple NTLMv2 problems >> between vista and samba. >> But one step after the other: >> My setup: >> - coLinux 0.8.0 (devel-20080329) from Henry Nestlers site >> - TAP Win32 version 8.4 from Henry Nestlers site >> - ubuntu 7.04 >> - Windows Vista Ultimate >> - manually start coLinux (not as a deamon) >> >> After setting up everything and starting coLinux - it seems to work. My >> tuntap adapter works with IP 192.168.0.1 on Vista and 192.168.0.2 on >> ubuntu. The ssh-Login works and so on. After mapping a samba drive from >> ubuntu into vista I can see my files and work with them. >> BUT after approx. 15 Minutes the samba connection "blocks". The other >> network connections like ssh are still alive and I can work with them; >> but samba blocks. I've installed wireshark to see what happens and I >> see, that directly before samba blocks vista sends a bunch of (UPNP) >> multicast messages (IP 239.255.255.250) to ubuntu - and after that - the >> samba connection seems to be broken !! from the vista point of view !!. >> The samba server itself still sends echo-requests and is alife. The >> reason, why I ask this question here is: If I set up a Microsoft >> loopback-device with pcap-bridging - the connection stays stable - but >> very very slow. In my opinion this may be a problem in the tuntap driver >> or in coLinux. >> Are there anybody here who knows this problem or has any suggestions? >> >> Thanks in advance! >> >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference >> Don't miss this year's exciting event. There's still time to save $100. >> Use priority code J8TL2D2. >> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone >> _______________________________________________ >> coLinux-users mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-users >> >> >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |