For example, the Max was originally configured with just 1 IP address (let's say 200.200.200.1). When I assign it a second IP address (let's say 100.100.100.1) it accepts it and sets up the proper routes because the dial out connection is active.....I can ping out to the Internet from the MAX on the secondary connection. The problem comes when I try to change any of the workstations on the Ethernet from being on 200.200.200.xxx to being on 100.100.100.xxx.......The workstations report an IP address conflict with the MAX's Ethernet MAC address.....This happens on all of the workstations trying to use the 100.100.100.xxx network...... Is there something that I am missing....????? Is this not possible.....???? ? TIA _________________________________________________ Alex Simpson Director of Technical Services NetSolutions Corp 615.367.4404 Voice x101 615.367.3887 Fax 615.303.7411 Pager Alex@NSCorp.net <A HREF="http://www.NSCorp.net">http://www.NSCorp.net</A> <A HREF="http://www.connect-ed.net">http://www.connect-ed.net</A> Airport Executive Plaza 1321 Murfreesboro Rd Suite 721 Nashville, TN 37217 _________________________________________________ ---- From: Jon Rust <jpr@vcnet.com> To: ascend-users@bungi.com Date: Thursday, June 05, 1997 1:45 PM Subject: Re: (ASCEND) Ascend QA gone downhill? >>+ MAX 4004 fried a dm12 after s/w upgrade (BTW, took over a week to get a >>new one) > >Weird, how did a software upgrade "fry" hardware ? You tell me. All six cards worked with 4.6c. I upgraded to 4.6ci26 (the latest available at the time), and one of the cards disappeared. Ascend tech support didn't believe me either. They insisted on telneting into the MAX before resigning, and issuing an RMA -- which was promptly lost, hence the week delay. The replacement card plugged right in and worked immediately. >>+ P75 with DOA ethernet >> >>+ P130 w/DOA ethernet >> >>+ 2 P130's with bad flash (won't take any upgrade, stuck at 4.6c) > >This is not the "fat" loads problem I assume ? Are these being upgraded >via tftp ? As it turns out (sheepish grin), one (1) of the memory problems turned out to be the "upgrade to 5.0a first, then 5.0ai10" problem. However, the other is really fried. Even a simple fclear returns an error. Unfortunately, Ascend won't ship a replacement (unless we pay $500), so I'm trying to figure out how to keep the customer up, while their unit is shipped away for 10 days. Jon ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request@bungi.com To get FAQ'd: <<A HREF="http://www.shore.net/~dreaming/ascend-faq">http://www.shore.net/~dreaming/ascend-faq</A>> or <<A HREF="ftp://ftp.shore.net/members/dreaming/ascend-faq.txt">ftp://ftp.shore.net/members/dreaming/ascend-faq.txt</A>> ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request@bungi.com To get FAQ'd: <<A HREF="http://www.shore.net/~dreaming/ascend-faq">http://www.shore.net/~dreaming/ascend-faq</A>> or <<A HREF="ftp://ftp.shore.net/members/dreaming/ascend-faq.txt">ftp://ftp.shore.net/members/dreaming/ascend-faq.txt</A>> </PRE> <!--X-MsgBody-End--> <!--X-Follow-Ups--> <!--X-Follow-Ups-End--> <!--X-References--> <!--X-References-End--> <!--X-BotPNI--> <HR> <UL> <LI>Prev by Date: <STRONG><A HREF="msg00902.html">Re: (ASCEND) Banner Formatting Codes</A></STRONG> </LI> <LI>Next by Date: <STRONG><A HREF="msg00880.html">Re: (ASCEND) Serial #'s</A></STRONG> </LI> <LI>Prev by thread: <STRONG><A HREF="msg00908.html">Re: (ASCEND) dial up problem with bridging</A></STRONG> </LI> <LI>Next by thread: <STRONG><A HREF="msg00882.html">(ASCEND) Radius session time limit</A></STRONG> </LI> <LI>Index(es): <UL> <LI><A HREF="mail2.html#00881"><STRONG>Main</STRONG></A></LI> <LI><A HREF="thrd34.html#00881"><STRONG>Thread</STRONG></A></LI> </UL> </LI> </UL> <!--X-BotPNI-End--> <!--X-User-Footer--> <!--X-User-Footer-End--> </BODY> </HTML>