Re: Clients get disconnected / Server hangs

From: Jason Bourne (j_bourne_treadstone_at_hotmail.com)
Date: 09/01/04 

Date: Wed, 01 Sep 2004 15:04:52 -0400

Dirk Wagner wrote:

[snip]
>
>
> I already changed the NIC in the server (from Realtek to 3Com) and did
> the same at all Win2K clients.
> I changed the patch cables and also the switch.
> After dooing so, the system was running fine for a longer time, but
> finaly failed also. In the meantime the behavoir is the same as
> before...
>
> Any ideas?
>
> Thanks
>
> Dirk
Greetings:

 Although I don't have anything of the solution sort some things
emerge from randomly firing neurons:

- Make sure the NIC isn't in a slot that shares an IRQ with anything

- I'm thinking it maybe isn't buggy driver code because of the change you
made. But if the hardware can somehow get eliminated as a variable it would
help.

- Possibly the version of Samba? Google around and see if others have been
seeing the same behaviour and if it is the common denominator. I believe I
have seen another post somewhere describing essentially the problem you are
reporting. Check the Samba logs?

- DHCP or static IP assignment? Is a DHCP lease expiring or attempting to
renew? If you're using a DHCP server how is the DNS server getting updated?

- DNS version and capabilities? Windows might be looking for SRV records if
they are setup to "register automatically with DNS" in the networking
setup. If you're running an older version of Bind that doesn't support SRV
records turn this off on the Windows boxen. Also, if you have WINS running
on the Samba box have the Windows boxen been configured to use it?

- There can be incompatibilities with different DHCP and DNS server
softwares. (I'm sort of assuming here that you're using static IP) But I
point it out as it can be problematic.

Like I said: no solution here, just some random thoughts on the subject in a
very general manner. If there is some sort of period related to the
malfunction it would be easier to pin down. Usually a hardware intermittent
becomes more frequent with a decreasing period until it finally fails. A
lot of times a software flaw/bug can be identified if an exact sequence of
events can reproduce the problem. Too bad you don't have a spare server box
to set up in parallel to see if the problem occurs on more than one
machine. This would point to a Samba flaw. Wish you luck in any event.

-Jason

Relevant Pages

  • RE: ADMT Profile and Client problems
    ... But AD required a DNS server in domain, ... In addition, as you said the the DHCP service also hold at NT side, please ... >>have full admin rights on both domains and the client device too. ...
    (microsoft.public.windows.server.migration)
  • Re: Phantom DNS server
    ... Dilan Weerasinghe wrote their comments ... >> advantage, to use a Windows machine for DHCP and DNS, ... > their DNS server, although all other settings are correct. ...
    (microsoft.public.win2000.dns)
  • Re: Access limitations(?), and moving to a simple LAN
    ... > I read somewhere that DHCP also returns DNS server addresses, ... Set the router to use DHCP on it's WAN port. ...
    (comp.sys.acorn.networking)
  • Re: DNS for a mobile domain member
    ... clients must use INTERNAL DNS. ... > laptops to automatically get a DNS server, which they do from the ISP, ... If they are using DHCP ... > exception that logging onto the home domain takes a very long time. ...
    (microsoft.public.windows.server.dns)
  • Re: Need help (of course) setting up network
    ... I'm' not a network expert, and others will probably correct me if I am ... > messages say that winbind fails. ... This makes me a DNS server doesn't ... I use samba without it. ...
    (Fedora)