Printable View
Im using Windows 2000 Server Service Pack 2 in our computer shop, the problem is ... then i access the workstations .. (which is using Windows 98 SE) it is too slow !!! but if im accessing Windows 2000 Professional/Server its fast.
Im using a CNET LAN card 10/100 MBPS and a CNET Switch, and i have a total of .. 12 PC's
Use wins, or try using netbeui for testing.
if it works with netbeui, then it is a tcp/ip problem.
most likley it has to do with win2k looking for the "scheduled items" and "printers" folder names on the 9x boxes.
If you think that is slow, try a mixed Novell / Win2k environment. Using a unc does not cut it.
(win2k pro for the desktop, mixed novell and win2k servers)
Is the switch 10/100?
Also try setting both NIC cards to Full 100 duplex and set the IPX to 802.3
[quote]Originally posted by kannibul:
<strong>Use wins, or try using netbeui for testing.
if it works with netbeui, then it is a tcp/ip problem.
most likley it has to do with win2k looking for the "scheduled items" and "printers" folder names on the 9x boxes.
If you think that is slow, try a mixed Novell / Win2k environment. Using a unc does not cut it.
(win2k pro for the desktop, mixed novell and win2k servers)</strong><hr></blockquote>
Wanna know whats really slow, a NT/Novell domain with Windows 2000 Workstations on dual IP. Wow now thats slow. Dual IP is so slow.
How do you have the server configured? is it a domain controller? is it a dhcp server or are your ips staticly assigned?
[quote]Originally posted by Weazel:
<strong>How do you have the server configured? is it a domain controller? is it a dhcp server or are your ips staticly assigned?</strong><hr></blockquote>
Nope it is not a domain controler, i didn't touch the dhcp server and my ips are automatically assigned.
[quote]Originally posted by Daemon:
<strong>Is the switch 10/100?
Also try setting both NIC cards to Full 100 duplex and set the IPX to 802.3</strong><hr></blockquote>
The switch is 10/100, all PC's are using CAT 5. i didn't enable the IPX, should i enable it?
[quote]Originally posted by kannibul:
<strong>Use wins, or try using netbeui for testing.
if it works with netbeui, then it is a tcp/ip problem.
most likley it has to do with win2k looking for the "scheduled items" and "printers" folder names on the 9x boxes.
If you think that is slow, try a mixed Novell / Win2k environment. Using a unc does not cut it.
(win2k pro for the desktop, mixed novell and win2k servers)</strong><hr></blockquote>
Hmm.. that's new! how do i do that ?
If you don't have a hybrid network i.e. MS and Novell, you don't need IPX. Assuming that it's an MS server/client, this is my suggestion:
Server:
Client for MS
File and Print sharing for MS
TCP/IP (if you need www access) or
NetBEUI (if you don't know what your'e doing) :D
Workstations:
Client for MS
File and Print sharing for MS
TCP/IP (if you need www access) or
NetBEUI (if you don't know what your'e doing) :D