|
The problems you will face, will depend a lot on how you have things set up. If CA is using a host table on the pc, every client will have to be touched. OTOH, if you are using DNS, just your DNS has to be changed. When we changed from TR to Ether, we had both interfaces active at the same time in the as400 and routed via a 3640 Cisco router between the two subnets for the PC's. Even without a router you can put a TR and Ether card in a NT (W2K) box and use it to route between your TR and E PC's if needed (if they only talk to the 400 you can skip this step). I would recommend this process if possible. I'm not sure what your asking about OPSNAV, but it should follow the DNS. If you have both interfaces active I would just add a "new connection" (use ip address for "system name" and it should work fine), you can always change it back to the name later. Make sure that if you have any hard coded ip's (Web connections, DDM files, pasthr sessions, LAN or RMTOUTQ printers) that your change them also. I'll be glad to answer any other questions that I can. David Boling Information Systems Director Rowan County -----Original Message----- From: Ted Barry [mailto:TBARRY@centralsan.dst.ca.us] Sent: Wednesday, February 13, 2002 6:58 PM To: midrange-l@midrange.com Subject: Network *CHG - Token Ring to Ethernet We're going to be switching from token ring to ethernet and of course we're doing a gradual migration. Aside from the fact that I'll have to change the interfaces and routes through CFGTCP, does anyone know what the impact of existing installations will be for Client Access? For example: When I run OPSNAV and look at the properties for my system it shows the old IP address. When I cut-over to the new address and modify the interface and routes, will this automatically modify the system name QSxxxxxxx. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.