!!!
great news !!! but really don't feel like reinstalling it all
i will try to reinstall binaries

I don't think you'd have to if some network guru could assist with a plain english answer (my network skills are only basic).

Here's what I observed.

Previously the internet connection to the gateway was on the same NIC/ IP address that SAMBA used.

This time I enabled both NICs on my mobo - eth0 = 192.168.0.16 and eth1 = 192.168.0.17

I configured general network access to (eth0 = 192.168.0.16)

After i got SAMBA up and running I observed it was using eth1 = 192.168.0.17

Now, while it sorta makes sense to me that using a separate NIC might make a difference, I do not have a clue how you'd configure SAMBA to use one or the other - seems the MDK installer might have doen that for me?

I suspect it is done with the INTERFACES directive in the SAMBA configuration. If it is I just wish there were some readable/ understandable instructions somewhere on what it means and how to configure it. - here's what one of my manuals says: The interfaces lists binds the interfaces parameters to the interfaces.

They shoulda been writing scripts for Monty Python.

I think it is high time for a "LINUX FOR DUMMIES" and "SAMBA FOR DUMMIES"

My worth

hey guys
i discovered that an iDeq 200N Mini PC experienced the same problem when connected to my server. And to my surprise, booted with a Knoppix CD, the problem was still here !

Guess what : the only thing in common between this pc and my other puter is the nForce chipset !

And by reading your last post, confiused_bof, it seems tha tyou have an integrated NIC on your mobo.. please tell me it's a nForce based motherboard !

i will try to switch it in the bios from Nvidia to 3com (i only have one jack but two chips can use it)... tomorrow.. for now, bed time !

Hi,
Sorry, but all mobos at the time were MSI- the onboard NICs are all SiS

But, a couple of new PCs have come into the office. They have Gigabyte 7N400L mobos and nForce chipsets. One of these is now the Samba server. Performance is excellent.

As I indicated earlier everything works fine, The only thing we've really changed is to take the ISP dial up off the Linux PC and put it on a Windoze box. Much easier to set up on WinXP anyway.


All the best

we'll never find the cause of this problem

This is the configuration of our small network

Three WinXP PCs, all running a single NIC (Network Interface Card). These go to a network switch. Just a cheap one, but it seems OK.

One of the WinXP machines has the dial up modem on it. It is the gateway, IP address 192.168.0.1 - I let WinXP configure this using the Wizard thingie (I'm lazy).

On the Linux PC there are two NICs, one configured for internet access via the WinXP hosted gateway 192.168.0.1, the other not. I used Mandrake's Control Center to configure eth0 and eth1.

Although it is probably not relevant, the IP addresses on eth0 and eth1 are 192.168.0.16 and 192.168.0.17 respectively.

A couple of days ago eth1 failed. Immediately the network performance dropped dramatically. The speed was something close to 56kbps, or the dial up modem speed. Clearly there is a clue there, but my networking knowledge is limited in this area.

I replaced the NIC, and speed immediately came back up.

That works for me, so I do hope this helps.

My next mission is to get the modem onto the Linux pc. However, I need to complete my Phd on "Linux Obfuscation" first so I can get my head around setting up a dialler daemon. The documentation of those I have looked at are an absolute nightmare. Sorry, I'll get off that soapbox.

Have a great 2004

IMHO Linux has reached my top list of crap i hate.


After now spending a total of 40 hours on a project that takes 2 hours to do using windows with no result i'm completely abhored at this "buiseness solution"

after following everything all the posts on this site say to do still nothing works.


Redhat 9.0 + samba 3.0
configured correctly.
was working fine yesterday...

picked up the computer put it down on a cement floor gently and left it there over night come back and suddenly out of no where this un-resolvable error comes out that i'm helpless to resolve.

It's slow, unbelievably slow. I can't mount images with it anymore... yes anymore since it was working...

You have my sympathies- I have been there and done that and much worse. IMO the situation is made all the worse by documentation writers who start off with pages and pages of why LINUX is a good thing and THEN, when they finally to get around to the issue, write in terms of extreme obfuscation. I nearly went mad trying cope.

I battled on and think I'm more or less on top of it now.

I assume that you have a local network and connect to the internet. In the matter of (SAMBA) performance, install TWO NICs (network cards) - configure one for internet access and the other for general local access. I use Mandrake and its control centre makes the setup very simple (not as simple as Windows, mind). I can clearly demonstrate how SAMBA performance dies in the arse when it is running on the same NIC as the internet connection. And before anyone comes crawling out of the woodwork to tell me that I need to edit abc.conf or xyz.conf or whatever, go away - I have it working!

The other issue on performance are graphic cards. If you listen to the posts, you can buy a new $200 card each week in the futile hope that this or that driver will install and work. And when it doesn't you'll be advised to recompile the kernel. And when the whole thing falls in a heap you'll be told how stupid you are.

ah... I feel so much better now - thanks for the soapbox.

And before the rest of you flame me, my MDK 9.2 with SAMBA is humming along. Everyday I seem to be doing more than playing Tux Racer with it. I am a happy Linux convert.

regards

Alriught I found a post somewhere else that told me to disable/stop the webclient service windows runs because samba is unable to fully emulate a windows server.

Well it was working for a total of 7 record breaking days of correct functionality. Then it decided to die... again.


Now my old post seems to have dis-appeared with no resolution.

I also noticed that if I happen to take my mouse away from the linux box, it decides that my keyboard should also stop working.

Sigh. If someone could recommend a better "flavor" of linux that would be great.