AW: Samba with WinXP
Hi, make sure, you created a valid linux account with the same username as your winxp user has. create a samba user with the same username smbpasswd -a and set the identical password as your windows user has and don't use a winxp user without a password. this should work. if you can still not connect please send your smb.conf peter -Ursprüngliche Nachricht- Von: ThanhVu Nguyen [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 12. Juni 2002 04:49 An: Debian User List Betreff: Samba with WinXP Hello, I have problem with connecting to the samba server on my Debian box from a WinXP machine. I can connect to the samba server from all my other Linux box but I just can't connect to it from an XP machine. I can see the Debian Samba server listing in the XP's WorkGroup place. I got a message "account not authorized to log in from this station" when I try to connect. Is there any different setting in WinXP , some registry edit etc ? tia -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
AW: sudden problems with masqueraded connections over a t-dsl line
many thanks karl, martin,waldemar and nicos, in deep my provider changed its behaviour when dealing with oversized packets. pinged ptp is still not possible, but this is only annoying if you do a traceroute. if anyone is experiencing the same problem, with kernel 2.4.3+ and recent iptables the following will fix this issues: iptables -A FORWARD -p tcp -o ppp0 --tcp-flags SYN,RST SYN -j CPMSS --clamp-mss-to-pmtu thanks peter -Ursprüngliche Nachricht- Von: Karl E. Jorgensen [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 11. Juni 2002 22:43 An: [EMAIL PROTECTED] Debian. Org Betreff: Re: sudden problems with masqueraded connections over a t-dsl line You got to fix those linebreaks; they were so bad I *had* to reformat things... And the odd uppercase letter wouldn't hurt either... Disclaimer: I'm not familiar with ADSL; I'm on dialup. On Tue, Jun 11, 2002 at 10:07:59PM +0200, Peter Lieven wrote: > since friday my isp german telekom changed some configuration in their > routers. > > everytime when i connect to remote host through my firewall who is > masquerading internal connections the connection to the remote host > freezes after a certain number of bytes has been transferred. I presume that "ping" works OK? (you probably checked, but it's not clear from what you write) > i changed nothing on my firewall config. i asked the isp to reset my > dsl port and check their equipment. i also changed the masquerading > port range in case they want to prevent their customers from > masquerading (don't ask why). > > when i ssh to my firewall and connect directly to the remote machine > everything is working fine. at the moment i installed some port > forwarders on my firewall to connect directly to a remote machine. if > i use them or a some other local proxy it works fine. only masqueraded > connections are stalling > > is there anyone out there who had the same experience or knows any > workarounds or has any ideas how i can find out what exactly freezes > the connection. I've been suffering the same sort of problems. Symptoms were: - Downloading of mail would work. Until a "big" email was being fetched, where it would appear as if the pop3 server just died (=timeout at my end) - Web pages would download fine, but very large images would only ever partially download - Setiathome would never manage to get a full work unit. >From the firewall itself, everything would work; but anything behind the firewall would suffer the above symptoms. My workaround was to lower the MTU on my dialup interface - an mtu of 750 and using the --clamp-mss-to-pmtu (man iptables(8)) in the firewall setup did the trick for me. I still doubt whether this is a *real* solution; it feels more like a work-around. Also, it introduces a bit more TCP/IP overhead (relatively speaking) and decreases the net bandwidth available. But it works for me. YMMV > one strange thing that came along with this that i'm not able to ping > my p-t-p partner, but its pingable from outside. i even used a > windows machine to do the dialip connection and nat via ics. same > strange behaviour. Sounds odd. But then I don't know ADSL, so I can't comment. HTH -- Karl E. Jørgensen [EMAIL PROTECTED] www.karl.jorgensen.com /"\ \ / ASCII Ribbon Campaign x - Say NO to HTML in email / \ - Say NO to Word documents in email (and Macros!) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
sudden problems with masqueraded connections over a t-dsl line
since friday my isp german telekom changed some configuration in their routers. everytime when i connect to remote host through my firewall who is masquerading internal connections the connection to the remote host freezes after a certain number of bytes has been transferred. i changed nothing on my firewall config. i asked the isp to reset my dsl port and check their equipment. i also changed the masquerading port range in case they want to prevent their customers from masquerading (don't ask why). when i ssh to my firewall and connect directly to the remote machine everything is working fine. at the moment i installed some port forwarders on my firewall to connect directly to a remote machine. if i use them or a some other local proxy it works fine. only masqueraded connections are stalling is there anyone out there who had the same experience or knows any workarounds or has any ideas how i can find out what exactly freezes the connection. one strange thing that came along with this that i'm not able to ping my p-t-p partner, but its pingable from outside. i even used a windows machine to do the dialip connection and nat via ics. same strange behaviour. thanks for your help peter
AW: apic errors / interface crash on tyan 200t
the apic errors (hundreds look like these) Jun 4 18:44:18 gw01 kernel: APIC error on CPU1: 02(02) Jun 4 18:46:04 gw01 kernel: APIC error on CPU0: 02(02) Jun 4 18:46:27 gw01 kernel: APIC error on CPU0: 02(02) Jun 4 18:57:51 gw01 kernel: APIC error on CPU0: 02(08) Jun 4 19:05:00 gw01 kernel: APIC error on CPU0: 08(02) and the device crash appears in the system log this way: Jun 4 19:05:00 gw01 kernel: unexpected IRQ trap at vector 6d Jun 4 19:05:03 gw01 kernel: NETDEV WATCHDOG: eth1: transmit timed out Jun 4 19:05:03 gw01 kernel: eth1: Transmit timed out: status f048 0c00 at 71460461/71460489 command 000ca000. Jun 4 19:05:03 gw01 kernel: eth1: Tx ring dump, Tx queue 71460489 / 71460461: Jun 4 19:05:03 gw01 kernel: eth1: 0 200ca000. Jun 4 19:05:03 gw01 kernel: eth1: 1 000ca000. Jun 4 19:05:03 gw01 kernel: eth1: 2 000ca000. after this eth1 is blown away. only a reboot brings it back to life any ideas? thanks peter -Ursprüngliche Nachricht- Von: Rainer Ellinger [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 5. Juni 2002 08:26 An: debian-user@lists.debian.org Betreff: Re: apic errors / interface crash on tyan 200t Peter Lieven wrote: > the problem is, that the bos runs into serval kernel apic errors and > sometimes when the load gets higher the second interface crashes and Unless only the nic and not the whole box does freeze, these two problems are imho supposed to be independent from each other. Kernel eepro100 driver is known to be broken. So give Intels e100 module a try: ftp://aiedownload.intel.com/df-support/2896/eng/e100-2.0.30.tar.gz > unusable. the only solution i found for this is disabling apic at > all. the box runs stable so far, but the second cpu idles at 99,9%. What error msgs do you get with APIC? -- [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
apic errors / interface crash on tyan 200t
i recently installed a new debian box (kernel 2.4.18smp) on a tyan200t with 2 p3 1ghz cpus. the box is one of our customer routers and runs iptables to trace the traffic on several ips. the two onbard intel ethernet interfaces are connected one to the backbone, the other to the customer switches. the problem is, that the bos runs into serval kernel apic errors and sometimes when the load gets higher the second interface crashes and becomes unusable. the only solution i found for this is disabling apic at all. the box runs stable so far, but the second cpu idles at 99,9%. this is not the way i want it to go. does anyone now about an other way to fix this problem. bios update, kernel patch, some other hack, special apic configuration, additional network cards? your help would be much appreciated, thanks peter
mailing list software
i'm confronted with setting up a mailing list with about 20-30k subscribers. i find mailman very useful, but i want to remove the password option. is there a patch available? which software is used for the debian lists? thanks, peter
