Hi all, we recently moved our offices to a bigger place. Therefore all our servers and network electronic had to be turned off... :) Well, I know it sounds odd but after the move Samba is much slower serving the shares and users have to wait ages for the information to be copied or moved across the network. In some cases, Windows desktops seem to freeze until the data is retrieved from the Samba server where the shares are hosted... Nothing has been changed nor modified. System and network configurations remain the same, smb.conf is the same on the server, we use the same IP range, gateways, etc etc. Any clues? Maybe I'm overseeing something really obvious... :-/ TIA, Martin -- *Martin Mielke* Senior Systems Administrator Casino.com Envelope *Email:* martin.mielke@casino.com The contents of this email and any attachments are for the intended recipient(s) only. This email may contain proprietary, confidential, or otherwise private information belonging to Casino.com (hereafter referred to as "The Company") or its affiliates. The Company does not take any responsibility for, or endorse any information which does not relate to its official business, including personal mail and/or opinions by senders whether or not they are employed by The Company. If you receive a message that was not intended for you, please notify the sender immediately (or forward the email to privacy@casino.com <mailto:privacy@casino.com>). Do not read, use or disclose the contents in any way and delete the message immediately. The Company will take reasonable precautions but cannot ensure that this e-mail and any attachments will be free of errors, viruses, interception or interference. Therefore The Company can not be held liable for any loss or damages incurred by you which have been caused by any of the foregoing. No undertaking, guarantee or other obligation contained in this email or any attachments will bind The Company unless it is later confirmed in writing.
Martin Mielke, on 12/28/2007 12:11 PM, said the following:> we recently moved our offices to a bigger place. Therefore all our > servers and network electronic had to be turned off... :) > > Well, I know it sounds odd but after the move Samba is much slower > serving the shares and users have to wait ages for the information to be > copied or moved across the network. In some cases, Windows desktops seem > to freeze until the data is retrieved from the Samba server where the > shares are hosted... > > Nothing has been changed nor modified. System and network configurations > remain the same, smb.conf is the same on the server, we use the same IP > range, gateways, etc etc. > > Any clues? Maybe I'm overseeing something really obvious... :-/First, I'd be looking at any changes that were made since last reboot - many times I've been bit by some change that doesn't get applied until a reboot. Other possibilities are a bad port on a switch (the one the server is on, since its affecting everyone) or a mismatched duplex mode on either the switch or server side of the network connection. -- Best regards, Charles
Jeff Ross wrote:> Martin Mielke wrote: >> Charles Marcus wrote: >>> Martin Mielke, on 12/28/2007 12:11 PM, said the following: >>>> we recently moved our offices to a bigger place. Therefore all our >>>> servers and network electronic had to be turned off... :) >>>> >>>> Well, I know it sounds odd but after the move Samba is much slower >>>> serving the shares and users have to wait ages for the information >>>> to be copied or moved across the network. In some cases, Windows >>>> desktops seem to freeze until the data is retrieved from the Samba >>>> server where the shares are hosted... >>>> >>>> Nothing has been changed nor modified. System and network >>>> configurations remain the same, smb.conf is the same on the server, >>>> we use the same IP range, gateways, etc etc. >>>> >>>> Any clues? Maybe I'm overseeing something really obvious... :-/ >>> >>> First, I'd be looking at any changes that were made since last >>> reboot - many times I've been bit by some change that doesn't get >>> applied until a reboot. >>> >>> Other possibilities are a bad port on a switch (the one the server >>> is on, since its affecting everyone) or a mismatched duplex mode on >>> either the switch or server side of the network connection. >>> >> >> Hmmm... >> >> Both Samba server and switches are configured to use the same speed >> and duplex mode. >> >> Samba server: >> --- >> # ethtool eth0 >> Settings for eth0: >> Supported ports: [ TP ] >> Supported link modes: 10baseT/Half 10baseT/Full >> 100baseT/Half 100baseT/Full >> 1000baseT/Full >> Supports auto-negotiation: Yes >> Advertised link modes: 10baseT/Half 10baseT/Full >> 100baseT/Half 100baseT/Full >> 1000baseT/Full >> Advertised auto-negotiation: Yes >> Speed: 100Mb/s >> Duplex: Full >> Port: Twisted Pair >> PHYAD: 1 >> Transceiver: internal >> Auto-negotiation: on >> Supports Wake-on: d >> Wake-on: d >> Link detected: yes >> >> --- >> >> The switch is set to 100-FDx (100baseT/Full Duplex), so everything >> matches... >> >> Still confused... >> >> >> Cheers, >> Martin >> > > Any chance you've accidentally got a loop going between switches? > (i.e. two cables connecting two switches instead of one?) > > JeffNope. I also thought of that :-) Cheers