similar to: Need help seeing Samba Server from WinXP

I have literally beat my brains out trying to get my XP machine to talk to my samba server on my linux machine. MY PROBLEM: The samba server (version 2.2.7a) is running on Redhat Linux 9.0. I can successfully connect to the XP machine and copy files from the XP machine to my Linux machine. But I cannot access my linux box from my XP machine (The samba server shows up in the browse list on

I recently ran into significant problems with a network configuration in which transfers from the samba linux box to a windows box was taking a unreasonbly large amount of time. Transfer speeds looked like 5k/sec vs ftp with the same file/machine setup, 750k/sec. I found a solution to my problem. My problem I think was something the duplex mode whether it was incorrectly configured in the driver

I've got a 2.6.8 kernel with bridging enabled as a module, two nics (LNE100TX and RTL8139) and i've run the following commands with no errors modprobe -v bridge brctl addbr br0 brctl addif br0 eth0 brctl addif br0 eth1 both interfaces have 0.0.0.0 as their addresses and brctl showmacs br0 shows the macs for both internal cards. However, bridging doesn't seem to be working at all.

I previously posted this to the linux.samba mailing list. I'm not sure that was the right place, so here it is again. Apologies if you've already seen it. Hi, I would really appreciate any hep with a big problm I'm having with XP (Pro / SP1 ) transferring to a samba share. The transfer starts off OK, using about 66% of my 100Mbs network. Then, after about 10-15 seconds, it drops off

On Thu, 24 Feb 2005 15:26:43 -0700 Bryan Waters <bryanw@abwaters.com> wrote: > I'm trying to debug my bridge...i've sent an email to the list but i'm > not yet approved by the moderator. Can you help me? > > thx > -bryanw > > ---------------------------------- Email to Bridge Mailing List > ----------------------------------------- > I've got

Greetings all: I currently have three Windows NT 4 domains. I'm evaluating the switch to either (at least) a mix of RedHat Linux or a total switch to RedHat. For file serving processes, I'll utilize SAMBA. For my first test, I've been looking at/trying to duplicate and then replace the services of my least obtrusive server - our Proxy Server - with an older workstation for the Linux

Update on the problem all: Turns out a junior administrator had used the IP addy that I was using for my test machine for another machine and didn't tell me about it. Anyway - MAJOR problem averted, but I still have a minor annoyance. I described a very long pause when accessing the SAMBA machine from Windows before, well that is still with me. I finally get what I'm looking for, but it

Well the weekend didn't bring any solutions to this unhappy camper. I spent most of my time trying to narrow down the problem again. I started out by installing a quick copy of ZipSlack on the Win98SE machine to determine once and for all if the problem was a Windows problem or not. Well, I tried a simple FTP from the ZipSlack to my Mandrake 8.0 server and it hung up like in Windows. So I

Well as a further to my last, I broke down and put a copy of Win98SE on a spare HDD in my Mandrake server box. First moment it was up and running, I tried to transfer the files between the two problem computers and BINGO! It worked. So sadly I must assume that the problem must lie on my Linux server :( As I have previously tried both Mandrake 8.0 and Redhat 7.1 and end up with the same transfer

Bug report follows. Please CC me if you want me to read the reply, as I'm not subscribed to ext3-users. [1.] One line summary of the problem: Ext3 has just causing filesystem corruption which required fsck to fix. [2.] Full description of the problem/report: I just had my machine lock up with an ext3 oops, preceeded by a bunch of error messages in the logs. On rebooting, after replaying the

Hello, I am trying to solve a problem that I can foresee when I deploy Asterisk into a few SOHO situations soon. In Nebraska and in my area of Western Pennsylvania we have violent thunderstorms in spring and summer and sometimes very heavy wet snow in Winter. Both type of event will take out the power of a period of 30sec to 36-hours. So no UPS system would be able to handle a system for over

I use samba 3.0.10 on my linux box and I would like to access to a winXP LSD (it's a kind of light windows based on Service Pack 2 (SP2)). Unfortunately, it doesn't work although it worked with a SP1 windows. Here is what I have done : $ smbclient -L ip_winxp .... added interface ip=192.168.0.4 bcast=192.168.0.255 nmask=255.255.255.0 Netbios name list:-

Thanks for the answers so far but I haven't been able to come up with an solution yet :( Some new info (see bottom of email for history): 1. I upgraded to 2.0.10 on my Mandrake 8.0, no change to the transfer problem. 2. I attempted to ftp a file from the Win 98SE PC to my Samba Server, didn't work. So I can assume that it is not specifically Samba problem. 3. I have changed the NIC cards

Hello, I have something like this: SIPUSER <-sip-> ASTERISK <-oh323-> AUDIOCODEC <-e1-> PSTN After calling from SIP to PSTN (and from PSTN to SIP too) I can't hear anything only in my SIPUSER. At the PSTN side everything is OK. I have another network with another h323/sip (in the place of asterisk) and there everything is OK. In AUDIOCODES logs I see that everything goes

Hi All. I'am using Asterisk with SER. I can make call between two internal VoIP gateways or from na internal to external VoIP gateway. But when I get a external call, this call hang ups 5 seconds after and I reveive the following messages *CLI> -- Executing Dial("SIP/16008-3d17", "SIP/16007&SIP/16006|20|tr") in new stack -- Called 16007 -- Called 16006

Hi, The only reason I use Samba is I want to connect my linux desktop with my windows laptop and share the larger disk with the laptop. I got weird problem that I could only write to the samba server but I could not read from it with errors like: [2001/03/04 16:36:38, 0] lib/util_sock.c:write_socket_data(540) write_socket_data: write failure. Error = Broken pipe [2001/03/04 16:36:38, 6]

Hi, I have collected a bunch of old PII PCs that I am trying to PXE boot. There NICs are old and so I use etherboot floppy to emulate a native PXE boot. I have configured tftp, dhcpd, pxelinux, and all the other stuff. Everything works fine till pxelinux start booting. Then it stucks after printing the IP row. --------------- pxelinux output ----------------------- PXELINUX 3.10 2005-08-24

OK, Something wacky. I'm getting many, many of these, it just keeps building: --snip-- netstat -vat: tcp 0 0 192.168.103.99:http statusurl.e-gold.com:57015 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:26377 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:64279 SYN_RECV tcp 0 0

I thought that the below email would be of interest to LARTC readers. I wasted quite a bit of time tracking down this "feature" (bug?). Any comments that shed light on this would be appreciated. In short, "tc filter" + htb + bridging works only with ip_forward off. Andrew Athan ----------------------------------------------------------------------- All: It seems that

Hello I'm trying to set up Asterisk on an older AMD Duron 700MHz with Fedora 5 for use with SIP phones and the Linksys 3102 SIP gateway (ie. no FXO card, so no need for zaptel and libpri), but I'm stuck: The GrandStream BudgeTone phone fails registering with Asterisk :-/ Following the "Asterisk - The Future of Telephony.pdf", here's what I did: 1. Installed Fedora 5,