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
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
