Thanks for everyone who contribute into my question. I managed to resolve the problem with Cisco engineer on the phone after struggling for about an hour (yeap, I open a TAC case). The problem lies on the client. The Novell server 3.12 were using both 802.3 & 802.2 but in our router we only encap 802.3. However on the client most of them set the frame-type to 802.2 so if I login or do rconsole to the remote server, I can see the IPX traffic (sh ipx traffic) is receiving tons of mismatch frame type. Just some additional info for you guys, ever think of how to encapsulate 2 type of frame-type over a physical interface? Use sub-interface! Maybe this is a common answer but it's worth to learn this way. Jmata: You were right and I left out the serial ipx number. It's a very helpful info. Thanks! Oh btw they are removing the analogue circuit (bridging) and of course with the same external IPX network number will not work with router. Reason? Please read the next line. whatshakin: I could view all the servers remotely back and forth (only between servers). Sorry that I didn't include this on my question. However I did not quite agree with your opinion, I feel that the external IPX network number should be different over WAN with router. If client A sent a packet to client B through a same IPX network number, the router will treat it as local thus no packet will forward to the remote B router. Similar to IP if the IP subnet belong to local, it will not route it over the other site. Dave: Thanks for the reminder. Glad to be in this group. Ryan ---------------------- Forwarded by Ryan Ngai Hon Kong/GHL Technologies/MY on 08-08-2000 09:27 AM --------------------------- To: Ryan Ngai Hon Kong/GHL Technologies/MY cc: Subject: Re: IPX routing question. (ScanMail Checked: Virus Free!) Not entirely versed in routing IPX, but I am going through the same thing and came across the same problem. What one of my very high paid consultants told me was that I was missing an IPX network number on my serial ports. In your case I'm picturing the following: Before: Novell A (802.3, Net 888) ---------Microm ------Analogue lease ------Microm --------- Novell B(802.3, Net 888) After: Novell A (802.3, Net 888) ------- 1602 -----64k ----------1602 ---------------- Novell B (802.3, Net 887) Recommendation Novell A (802.3, Net 888) ------- 1602(ENCAP SAP, NET 889) -----64k ----------(ENCAP SAP, NET 889)1602 ---------------- Novell B (802.3, Net 887) I'm currently running Netware 4.11 and will soon be upgrading to 5.0 and converting to IP. Also look at the configurations and make sure that the IPX ROUTING (net #) is unique on each of your routers and that they represent you individual router. I got caught with this one when I was following a printed sample off one of the books I was using and after hours of troubleshooting, I disabled IPX ROUTING and re-enabled it and saw that the number had changed. Once I had that and the IPX NET #s on each of the interfaces things started working. Just out of curiosity, did the bridging keep working after they changed the circuit type and before you made the bridging to routing changes? Hope this helps. ---------------------- Forwarded by Ryan Ngai Hon Kong/GHL Technologies/MY on 08-08-2000 09:27 AM --------------------------- Please respond to "whatshakin" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: (bcc: Ryan Ngai Hon Kong/GHL Technologies/MY) Subject: Re: IPX routing question. I guess your problem is that now the computers on one network cannot see those on opposite network right? Anyhow, Novell 3.X and 4.X require the same identical EXTERNAL network numbers. By the looks of what you have given us you need to revert the 887 network back to 888. Make sure your frame type is consistent across the network too. Changing hardware should not make any difference. Perhaps someone with first hand experience can confirm this. Do some double checking on the modems to make sure they are working correctly. HTH Let us know how you fare. To: "'whatshakin'" <[EMAIL PROTECTED]>, [EMAIL PROTECTED] cc: (bcc: Ryan Ngai Hon Kong/GHL Technologies/MY) Subject: RE: IPX routing question. Each lan has to have its own IPX network number. Then on the serial interfaces of your routers (or subinterfaces), you have to have an ipx network on those as well. On the serial interfaces though, the ipx network number has to be the SAME between two sites. You also need to make sure you're using the same frame format, i.e. novell-ether, sap (802.2 or 802.3)See below: Site A, lan ipx 1234 ----Cisco Wan ipx 3456 ------- Cisco Wan ipx 3456 ----- Site B, lan ipx 7890 HTH, Dave ___________________________________ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
