Slow performance - migration IPX toIP

i assume you moved from netware to nt?
netware works more efficiently as a file server, so basically netware is faster than nt. it's expected that the network slows down.

Did you remove the IPX protocol from the clients? This could have an effect on speed on the network - IPX tends to take over and the clients may be trying to browse over IPX before IP. I've even seen cases where having IPX installed prevented a client from even seeing an IP network on older 95 clients. Hope this helps!

I believe that TCP-IP also has the greatest overhead of the major protocols, thus will compete for more system resources than the previous protocol.

There is no issue such as "performance degradation" when you have migrated from IPX to IP on a network. The implementation strategies, if not followed exactly, may degrade the network performance. Visit the following weblink for exact and standard procedure to migrate from IPX to IP.

http://developer.novell.com/research/appnotes/1999/june/03/04.htm

This is a generalized solution to the strategy.

Did you move from Netware to NT? or simple ipx wks to ip protocol.
1.- IPX is a wonderful protocol unbeatable performance in a local lan with no more than 300 devices.
If you don't have branches or IP specific aplications there?s no reason to move.
Netware has better performance than Windows NT working as a file server.
Provide me more info and I will be able to more specific.

Assuming that you are on a Microsoft network, the following leads are provided for your review.

First, consider upgrading from Windows 95 to Windows 98 or later operating system.

Microsoft Windows clients use different methods of host name to IP address resolution. The sequence of methods is different than the sequence used to resolve NetBIOS names to IP addresses.

When Windows 95 tries to resolve a NetBIOS name using a NetBIOS name server, it first checks a Windows Internet Name Service (WINS) server, and then checks a DNS server (compare this order when reviewing the Microsoft Knowledge Base articles listed below).

When using Windows 95 and DNS, one should use a WINS server for NetBIOS name resolution. Under most circumstances, the default resolution order does not need to be changed. However, to overcome the problems with your Windows 95 clients, changes will have to be made. The following Microsoft Knowledge Base articles should help in your decisions.

Q172218
Microsoft TCP/IP Host Name Resolution Order

Q119493
NetBIOS over TCP/IP Name Resolution and WINS

Q170619
Windows 95 ServiceProvider Priority Values
Not Applied

Q171567
Windows NT 4.0 ServiceProvider Priority Values Not AppliedQ139270
How to Change Name Resolution Order on Windows 95 and Windows

Q119372
Setting the Name Resolution Search Order for TCP/IP-32

File Names: tcpimp2.exe (Tcpimp2.doc zipped) at:

ftp://ftp.microsoft.com/bussys/winnt/winnt-docs/papers/

Titled: Microsoft Windows NT 3.5/3.51/4.0: TCP/IP Implementation Details TCP/IP Protocol Stack and Services, Version 2.0

This question was auto closed due to inactivity