Topic: maped network drive keeps dying w2k

[darren]

i have several machines running win98 and win 2k and the machines with Windows 2000 the mapped network drives keep dying i.e when i try to access the drive it says the connection has been closed i press ok then it finds the drive and i have access again, Is there a keep alive i need to run.
i have no problems with the win98 machines.

[Kevin]

We need a mor detailed description of the problem

Ex. version of e-smith, samba and look at the log files for samba etc....

[darren]

i am running sme 5

and samba 2.2
 and i just had that problem and i found this in the smbd.log
[2001/12/07 13:36:57, 0] smbd/server.c:sig_hup(384)
  Got SIGHUP
[2001/12/07 13:36:57, 0] param/loadparm.c:map_parameter(1986)
  Unknown parameter encountered: "share modes"
[2001/12/07 13:36:57, 0] param/loadparm.c:lp_do_parameter(2605)
  Ignoring unknown parameter "share modes"
and this in log.techsupport

2001/12/17 13:26:35, 0] lib/util_sock.c:matchname(955)
  host name/name mismatch: pc-00047 != pc-00047.tlccs.com.au
[2001/12/17 13:26:35, 0] lib/util_sock.c:get_socket_name(1008)
  Matchname failed on pc-00047 192.168.1.47


my machine is called techsupport and the ip is 192.168.1.47

[Kelvin]

Darren,

What is the brand / chipset of your network card in the W2K PCs ?

A number of cards (Accton Cheetah 10/100 cards are a good example) will give you this exact problem even when logging on to a "real" NT / W2K Server. It is a problem with the card drivers. While there may be an updated card driver that's fixed this problem, in most cases, I found it much simpler to just change network cards to a different brand (like simple Realtek based cards, 3COM or even Intel cards) and the problem goes away.

M$ knowledgebase has a few articles about this problem but NONE of the suggested workarounds actually works in these cases and a network card change is the easiest way to overcome the problem.

Regards,

Kelvin

[darren]

the cards i am using is a realtek8139 but ill try some new drivers

[Kelvin]

Hmm,

I've never had problems with my Realtek 8139 cards before.

One of the reasons given on M$ knowledgebase for this behaviour is something called AutoDisconnect -- a timeout figure set within the NT / W2K server. Like I said before, whenever I came across this problem the workaround given ny M$ does not work in my case, and changing NICs do. Again, I've not had problems with my 8139s before.

Let us know how you go with new drivers. Good Luck !

Cheers

Kelvin

[darren]

the weridest problem is that i still have access through to my database mysql
internet and ssh it only happens to the samba

[Kelvin]

Exactly like the problem with the NT/W2K Servers. It does not stop access to any other services just the mapped drives.

Kelvin

[hout]

This topic is a bit old.

But....

I have the same problem, does anyone know how to handle?