Hello I have basically a suse samba server setup. Eth0 is for the internet connection (cable). Eth1 is my internal network. I use eth1 for my samba server. When i have the shares/ drive letters mapped, whatever, Ill goto access them and that computer will just lockup or timeout for about 1 minute, then it will resume operation normally. I have approx. 5 comptuers on the suse server, and they all do this from windows xp to windows 98se. I am using set up addresses of 192.168.0.x, where is greater than 2. My question is have or is there something Ive setup wrong to cause this pause to occur. ? Its becomming very annoying..and frustrating. Im using kernel 2.4.18-64GB-SMP with a dual processor setup. If anyone has any ideas please let me know. Every package installed is orginal versions from the suse install cdroms. (no updates done). Anything come to mind. btw, ive replaced the switch, with a new netgear one, and all the networks at startech ST100 Realtek 8139 chipsets on 100Tx. Anyone... !
On Jan 23, jonathan <jcarron2@cogeco.ca> wrote:
When i have the shares/ drive letters mapped, whatever, Ill goto access them and that computer will just lockup or timeout for about 1 minute, then it will resume operation normally. I have approx. 5 comptuers on the suse server, and they all do this from windows xp to windows 98se. I am using set up addresses of 192.168.0.x Your problem are DNS lookups. You don't have a DNS server for your internal addresses, but someone tries to resolve them. Easy way: Edit your /etc/hosts and put all machines in it, enable WINS Server for samba and configure all machines to use the WINS server. I think, that you have to tell samba, that it should use dns/hosts lookup for wins queries, but you'll find out I guess ... More approriate way: Install bind9 and put up a zone file with an internal domain (e.g. yourcompany.net). Enter all machines there and use the samba server as DNS server for all clients.
Markus -- __________________ /"\ Markus Gaugusch \ / ASCII Ribbon Campaign markus@gaugusch.at X Against HTML Mail / \
Hm, the problem is your workstations try to browse the lan and don't know who is out there. DNS is a good thing, but for TCP/IP Networking it is normally not needed, because you wil need the browselist or a lmhost file. For this you can: a) Make a lmhost file like in C:\WINNT\system32\drivers\etc\lmhosts.sam with all your machines listed and your workstations don't have to browse the lan. Copy this file to all workstations (XP: c:\winnt = c:\windows !!!). b) Build up a samba-server with wins-proxy enabled and use it as wins-server in your network setup. c) Use NetBEUI-protocoll for hostresolution (is it part of XP? I think they left it somewhere on the setup cd in an extra folder). d) Setup a Samba-server as PDC and he will do for you the browselist. Disadvantage is, that the clients (mostly XP,2000,NT) want to be masterbrowser and sometimes win elections, if os-level is not propper set in /etc/samba/smb.conf. b) is the fastest way I know. We use it for 90 Workstations in our LAN in a students residence. Philippe P.S.: Here is my global section of my samba wins-proxy: [global] # fake all windummies it is a w2k server :-) announce version = 5.0 browseable = no domain master = no share modes = yes socket options = SO_KEEPALIVE TCP_NODELAY IPTOS_LOWDELAY wins support = yes max log size = 1000 preferred master = yes # !!! change x.x.x.x to your IP !!! # bind only one nic to samba (the internal one !!!) interfaces = x.x.x.x/255.255.255.0 socket address = x.x.x.x bind interfaces only = yes volume = Meister security = share # some simple "virus protection" veto files = /*.eml/*.nws/riched20.dll/*.{*}/*.rar/*.scr/*.exe/*.bat/ available = no server string = Serverkeller workgroup = WOHNHEIM local master = yes comment = Linux Box netbios name = Meister # I want to have logs for each machine log file = /var/log/samba/log.%m wins proxy = yes guest account = nobody os level = 33 guest only = yes load printers = no
On Thu, 2003-01-23 at 11:04, Philippe Vogel wrote:
Hm,
the problem is your workstations try to browse the lan and don't know who is out there. DNS is a good thing, but for TCP/IP Networking it is normally not needed, Since when? M$ got hold of a DNS server source code and modified so that win machines could 'Register with DNS' ... what a concept - clients inserting their own entries in a DNS zone ...
because you wil need the browselist or a lmhost file. For this you can:
a)
Make a lmhost file like in C:\WINNT\system32\drivers\etc\lmhosts.sam with all your machines listed and your workstations don't have to browse the lan. Copy this file to all workstations (XP: c:\winnt = c:\windows !!!).
If your network naming system (DNS, WINS, NIS, etc) is setup correctly, then this is not needed.
b)
Build up a samba-server with wins-proxy enabled and use it as wins-server in your network setup.
If you don't have a name server on the internal network yes, but if this is a home network with 3 pcs ... overkill.
c)
Use NetBEUI-protocoll for hostresolution (is it part of XP? I think they left it somewhere on the setup cd in an extra folder).
It is enabled by default (NetBIOS over TCP/IP) ... Be careful, if you disable this, then your Win98 machine will not talk to your WinXP or Win2K machines.
d)
Setup a Samba-server as PDC and he will do for you the browselist. Disadvantage is, that the clients (mostly XP,2000,NT) want to be masterbrowser and sometimes win elections, if os-level is not propper set in /etc/samba/smb.conf.
Why?
b) is the fastest way I know. We use it for 90 Workstations in our LAN in a students residence.
Philippe
P.S.:
Here is my global section of my samba wins-proxy:
[global] # fake all windummies it is a w2k server :-) announce version = 5.0 browseable = no domain master = no share modes = yes socket options = SO_KEEPALIVE TCP_NODELAY IPTOS_LOWDELAY wins support = yes max log size = 1000 preferred master = yes # !!! change x.x.x.x to your IP !!! # bind only one nic to samba (the internal one !!!) interfaces = x.x.x.x/255.255.255.0 socket address = x.x.x.x bind interfaces only = yes volume = Meister security = share # some simple "virus protection" veto files = /*.eml/*.nws/riched20.dll/*.{*}/*.rar/*.scr/*.exe/*.bat/ available = no server string = Serverkeller workgroup = WOHNHEIM local master = yes comment = Linux Box netbios name = Meister # I want to have logs for each machine log file = /var/log/samba/log.%m wins proxy = yes guest account = nobody os level = 33 guest only = yes load printers = no
DNS is a good thing, but for TCP/IP Networking it is normally not needed,
Since when? M$ got hold of a DNS server source code and modified so that win machines could 'Register with DNS' ... what a concept - clients inserting their own entries in a DNS zone ...
Oops, my mistake! I meant microsoft networks not tcp/ip networking <= layer 3. DNS is only required for internet connection with a router and whatever services require it. Since N$ networknames differ from the dns-entries! Wins acts as nns not dns. With a PDC (W2k) it is a litllebit more different. DNS is nice on your gateway, even with less pc's setup as DNS cache - multiple requests go faster by that way.
a)
Make a lmhost file like in C:\WINNT\system32\drivers\etc\lmhosts.sam with all your machines listed and your workstations don't have to browse the lan. Copy this file to all workstations (XP: c:\winnt = c:\windows !!!).
If your network naming system (DNS, WINS, NIS, etc) is setup correctly, then this is not needed.
Simple but won't refresh if your hosts change, so I would not use it. Samba can do this for you.
b)
Build up a samba-server with wins-proxy enabled and use it as wins-server in your network setup.
If you don't have a name server on the internal network yes, but if this is a home network with 3 pcs ... overkill.
If you have mixed environment and not very intelligent users putting their machines in a lan it is a nice feature as well.
c)
Use NetBEUI-protocoll for hostresolution (is it part of XP? I think they left it somewhere on the setup cd in an extra folder).
It is enabled by default (NetBIOS over TCP/IP) ... Be careful, if you disable this, then your Win98 machine will not talk to your WinXP or Win2K machines.
Notice NetBEUI is somehow different in XP, their made their own delicous soup in redmond with XP and M$ networks!
d)
Setup a Samba-server as PDC and he will do for you the browselist. Disadvantage is, that the clients (mostly XP,2000,NT) want to be masterbrowser and sometimes win elections, if os-level is not propper set in /etc/samba/smb.conf.
Why?
With 3 machines overkill, but I wanted to give some examples. Philippe
On Thu, 2003-01-23 at 11:51, Philippe Vogel wrote: <snip> Point taken ...
participants (4)
-
jonathan -
Markus Gaugusch -
Philippe Vogel -
Raymond Leach