6 replies
by ewilliams
by rbgnr111
by ewilliams
by jimbb
1. Make an inventory of your network apps. Not MS Office or so, but applications that use a protocol directly. Known is for example that ARCserve 6.x cannot work fully on a pure IP network. Upgrade or replace those apps.
2. Make an inventory of your queue based printers. How are they connected? Some older Jetdirect cards for example need to get a flash update before they can be configured to use IP, or be used via NDPS. Create NDPS printers for every queue you have. Check if there areapplications that still need queue based printing (like DOS apps that have to print to "LPTx"), and make sure an NDPS printer services those queues. Queue based printing does not function in pure IP.
3. Check your clients. DO they all have IP installed and bound to the client? This may be the time to upgrade all clients, and have them on the same version, and IP configured the way you want to.
4. Check if everything can communicate with everything over pure IP. Do you have routers that filter broadcasts? Then consider either opening the door (the netadmin will not like you) or using SLP.
5. Remove IPX as a test. Just disable it in INETCFG, and then select REINITIALIZE SYSTEM, and listen for howling users.
if num(howling users)>0 then restore IPX and check what you missed.
If you want to move to IP because it is a market trend, then it may be more trouble than it is worth. However, if you have a WAN or a few routers, then pure IP simplifies things, and it reduces traffic. You need IP anyway to surf and so, so why not use that alone.
Jim
by ewilliams
by ewilliams
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending