Win2k network question

[rsales]

I just installed Win2k on my main computer. Dual boot with Win98se. I got it working on the network but it is alot slower in opening a drive on another computer and changing directories than Win98se. Takes like half a minute to open a drive on another computer. Shows the moving flashlight like it's searching. Anyone know what's going on here? I didn't have this problem with NT4. I am not running tcp/ip on the lan.

 

[IsOs]

Inspect the LAN connection properties in Windows 2000. What protocol are you using? In the Advanced setting, check either media type or line speed, is it set to Auto or Half duplex?

 

[setaanbomb]

Well, your not using TCP/IP? You must be using Netbuei then. Netbuei is damn slow, don't ever expect performance.

I suggest using TCP/IP.

 

[rsales]

I have it setup for Client for Microsoft Networks and I believe it's using IPX for a prodical. As I said the other Win98se machines read a drive on another computer alot faster than the Win2k machine. I'll check the settings on the nic card for duplex. This is a dual boot machine and the Win98se works just fine. Win2k takes like 20sec for the intial find and read of the a drive.

 

[Shadow07]

You need to understand a few things here. First, what protocol do you have installed, TCP/IP, IPX, or something else?

When a Windows 2000 client tries to access a remote drive, it will try to connect to it using NTLMv2, which is the security provider in a Windows 2000 environment. If you have a KDC (Key Distrabution Center Server), it will try using Kerberos first. If the client cannot connect using NTLMv2, then it will use NTLMv1 (compatibility for Windows 9x and NT 4.0 and 3.5x machines). The reason for this is if you are trying to connect to a Windows 9x or NT machine (a non-Windows 2000 machine), it will try to connect by sending the current username and password. This will not work if you are connecting to a Windows 9x box, but it will work quicker if you are trying to access an NT machine.

What type of client are you trying to connect to?

 

[rsales]

Shadow07,

It's a home lan between three computers. No server. All machines have Win98se installed except for one which is dual boot with Win2k. I am not running a tcp/ip network. IPX prodical is loaded. The Win2k machine didn't communicate to the other computers until I install ipx which also installed NetBeui. Your explaination would explain the delay of ~20 seconds. I there anyway to keep it from checking for what is not there or is it just the nature of the beast. I don't remember having this happen with NT workstation.

 

[Nucleus111]

rsales-

I have a peer-to-peer network setup with win2kpro and win98se. Both machines can browse and share with no hesitation what so ever. I'm using both netbeui and tcp/ip. Check to see that ipsec is not being used on your tcp/ip connection and disable netbios. See if this gets you rollin'.

 

[Shadow07]

I would not disable NetBIOS. When you browse the Network Neighborhood, you see all of the computer names. NetBIOS is the protocol that controls the computer names.

If I were you, I would not install IPX/SPX, unless you are playing games that require IPX/SPX. I would just install TCP/IP on all of your machines. On your Windows 2000 machine, you will have to edit the registry for a setting you will need enabled. I do not have the exact key in front of me, but I am heading into work now and I will post it back. Basically, the key is to enable ISMASTERBROWSER and MAINTAINDOMAINLIST. Both keys are necessary in the network.

I'll explain in more detail when I post the keys.

BTW, make sure that you have a good backup of either your system, or of the registry.

 

[rsales]

I do play network games with the computers so I don't want to uninstall IPX prodical.