losing network drives

CableDude · Post by **CableDude** » Mon Nov 10, 2003 7:54 pm

Here is the scenario:

User has a windows 2000 machine logs into a domain (Windows NT Server) and two network drives are mapped to their machine.

last couple of days network drive disappears. restarting the windows 2000 machine sometimes fixes the problem.

Restarting the NT server does fix the problem till it happens again.

Thoughts?

I did find this, but have yet to try it

http://support.microsoft.com/default.as ... ct=win2000

Anyone ever experience this?

Thanks

CableDude · Post by **CableDude** » Tue Nov 11, 2003 8:11 pm

Post by **YeOldeStonecat** » Tue Nov 11, 2003 8:12 pm

You running login scripts? 2K and XP are usually quite good about keeping mapped drives. Sure they get that red X bug now 'n then...but the stuff is always there.

CableDude · Post by **CableDude** » Tue Nov 11, 2003 8:24 pm

Originally posted by YeOldeStonecat
You running login scripts? 2K and XP are usually quite good about keeping mapped drives. Sure they get that red X bug now 'n then...but the stuff is always there.

Yes there is a logon script on the NT server.

Post by **YeOldeStonecat** » Tue Nov 11, 2003 8:40 pm

NT Server has SP6.0a, and the other two major updates after that (Security Rollout Fix, etc)

What protocols being used?

How are the 2K machines setup..meaning, TCP details, how assigned, etc.

NT Server setup as a domain? Or stand alone?

CableDude · Post by **CableDude** » Tue Nov 11, 2003 8:47 pm

Originally posted by YeOldeStonecat
NT Server has SP6.0a, and the other two major updates after that (Security Rollout Fix, etc)

What protocols being used?

How are the 2K machines setup..meaning, TCP details, how assigned, etc.

NT Server setup as a domain? Or stand alone?

YOSC,

I'll have to look at the NT server side. My boss set that up.

2k machines were set up by me.

TCP/IP uses fixed IP address, gateway, wins server numbers.????

I believe the NT server is setup as a domain, but I'll have to look for sure.

Thanks.

Post by **YeOldeStonecat** » Tue Nov 11, 2003 9:01 pm

Originally posted by CableDude
2k machines were set up by me. TCP/IP uses fixed IP address, gateway, wins server numbers.????

And DNS.

On NT 4 Servers...DNS not as important to local LAN resolution as it is on 2K and 2K3 Servers. Referring to when you have 2K and XP clients...DNS is very important. But 2K and XP clients on an NT 4 server....I don't believe DNS is as important. Does he have WINS running on that server?

When the connections drop...can you still ping the server by name or IP? Can you still see it in network places? Try these next time it acts up.

Wondering if it's a connectivity problem...like a NIC on the server, or hub/switch.

When it happens...does it affect all clients at the same time? Or one client at a time acting screwy?

<==back online tomorrow....

CableDude · Post by **CableDude** » Wed Nov 12, 2003 8:02 pm

YOSC,

Here is what I was able to find out. NT server has the lastest SP.

Not sure about other updates because IE is version 5.0

I will be updating to 6 and install all the updates soon.

Network services are Computer Browser, MS TCP/IP printing, Netbios Interface, RPC configuration, Server, Workstation.

Protocols are Netbeui, Nwlink IPX/SPX compatible transport, NWLink netbios, TCP/IP.

The last time the problem occured it affected 5 2k machines. The only 5 that connect to the domain.

Thanks.

Post by **YeOldeStonecat** » Thu Nov 13, 2003 7:04 am

OK, long as she's recent in SP's...although that's not the reason for disconnects. No need to rush to install the latest IE, I'd probably not want to put past 5.5 on an NT 4 machine anyways.

How big is this network? Curious why IPX is loading, you have a Novell server too? What protocols are the clients using?

Try to check, next time it happens....from the clients...can you ping the server from the prompt. Can you browse it in network neighborhood.

Are the 2K machines the only clients? Or are there say Win9X clients who remain connected, when the 5x 2K clients bomb out?

Before you bounce the server next time it happens...check even viewer. App and System. Any red messages regarding the "server" service?

CableDude · Post by **CableDude** » Thu Nov 13, 2003 7:19 pm

Originally posted by YeOldeStonecat
I'd probably not want to put past 5.5 on an NT 4 machine anyways.

Great.

I was going to ask you about which IE version to install.

How big is this network? Curious why IPX is loading, you have a Novell server too? What protocols are the clients using?

Not sure why IPX is loading. Had a novell server but it's been out of commission for a while now.

Are the 2K machines the only clients? Or are there say Win9X clients who remain connected, when the 5x 2K clients bomb out?

There are about 3 98 clients and 2 95 clients

. The 98/95 clients seem unaffected when this happens.

I had the problem today again. Didn't see you post till now.

I did notice one thing, 1 machine (mine) didn't have the problem the other 4 did.

I also noticed that my machine had the netbeui protocol where the other ones did not.

I did not reboot the server this time. I rebooted the client machines and still no go. I then installed the netbeui protocol and the network drives appeared on reboot.

Still going to keep an eye on this. My machine has Sp4 the others have SP 3. I plan on updating to 4 soon.

Thanks.

Post by **YeOldeStonecat** » Thu Nov 13, 2003 8:04 pm

Well..hmmm...something funky here. Protocols...usually they don't decide to "just let go" in the middle of the day, either they work, or don't work.

The fact that all your other 9X workstations are fine...tells me it's not a local server problem, or problem with the server NIC, or most likely the switch the server is plugged into.

Something I'd look into...just because I like uniformity across the board...is the hideous mixmatch of protocols you have going on. I like everything the same...and as lean as possible. Small networks...NetBEUI is fine. But on bigger networks...NetBEUI creates too much chatter...clogs up your pipes. Officially on the MS books I think the number is..."Don't use NetBUIE on networks larger than 200 nodes". But most of us in IT prefer not to use it on networks of over 50 nodes.

IPX is very chatty too!

Most larger networks, especially with an NT server involved...TCP only.

But yours is pretty small. I'd groom those protocols...no harm leaving NetBUIE. What governs TCP/IP? A router? The NT server? Static IP's?

What about event viewer on the server?

Don't forget, if you play with protocols on an NT server, sometimes on a reboot you get error messages, often needs a service pack reapplied.

CableDude · Post by **CableDude** » Mon Nov 17, 2003 7:50 pm

YOSC,

These two protocols (Nwlink IPX/SPX compatible transport, NWLink netbios) are related to Novell, correct?

I'm guessing (though not sure) These disconnects have something to do with the shotty network that has been going down alot lately [virus traffic

]

Anyway, I'm going to due some further investigating latter this week.