>In any case, it definitely sounds like a routing problem since your IP is >in a different Class C than the remote's IP. Perhaps they are not routing >that subnet or Class C (whichever would be appropriate for them) to/from >their device that you're connecting to. Why in the world would that matter? For one if this was an IP pool, they would either choose a static route, or run OSPF. >It actually should have been less than two hours of work after your P75 was >configured (maybe two to four hours to get that just right), and they never >should have needed to bother Ascend. This should have only taken 5 to 10 min. >I serious don't think it could be a problem with the P75, unless it's >mal-configured. There would have to be a problem with the configuration in this case. Did the ISP say that everyone else is working in that block of IP's? First, when you connect, go into terminal serve mode, and ping the remote routers IP. Then try another one, like their DNS server. Chances are that you don't have the remote gateway set correctly, or you don't have a default route pointing to the correct remote IP. >>I am about to give up on ascend P75 or my ISP (www.stratos.net). >>Acsend seemed to blame Stratos. And Stratos seemed to blame >>Ascend. So who is at fault? I'll let you be the judge. >> >>ISP (Stratos) This doesn't matter... >>I have a single IP from them >> >>an IP address: 209.81.153.178 The above is your address for your router, however what is your subnet? It should be 255.255.255.255, or 209.81.153.178/32. >>remote address: 209.81.152.1 >>subnet mask: 255.255.255.192 This is fine.. However are you sure that you wrote this down correctly? I show the route going here: traceroute to 209.81.153.178 (209.81.153.178), 30 hops max, 40 byte packets 1 chi.fe5-1-alias1.map.interaccess.com (207.70.121.1) 1.275 ms 1.128 ms 1.1 31 ms 2 aads.good.net (198.32.130.49) 2.165 ms 1.807 ms 1.83 ms 3 megsinet.chicago.good.net (207.98.189.146) 26.445 ms 17.549 ms 14.753 ms 4 core1-s1-0.detroit.megsinet.net (208.150.63.2) 13.785 ms 20.851 ms 14.059 ms 5 core1-s1-0.cleveland.megsinet.net (208.150.58.66) 34.635 ms 38.47 ms 50.5 25 ms 6 gw1-e1.stratos.net (209.81.148.66) 67.244 ms 57.317 ms 25.662 ms 7 pm3-1.stratos.net (209.81.152.100) 42.149 ms 40.424 ms 36.765 ms 8 * * This clearly shows that you have the wrong IP for the remote router. It should be 209.81.152.100. >>Ascend >> >>firmware: 5.1A >>option 1: set p75 as 209.81.153.178 >> set my NT server to be 209.81.153.180 >> with subnet mask 255.255.255.192 >> and assign my 95 and BETA to be 209.81.153.179 and 209.81.153.181 >>result: can ping from p75 at termserv mode >> but none of the machines can ping outside of the LAN For one you can't do this. You said that your ISP gave you one IP. Now you are saying that you have 62 available addresses. This is probably a dialup IP pool. I would go with option 2 below, or by a LAN account with more IP addresses. >>option 2: use NAT >> set p75 as 200.200.200.200 >> set my NT server to be 200.200.200.202 >> with subnet mask 255.255.255.0 >> and assign my 95 and BETA to be 200.200.200.201 and >> 200.200.200.203 >> >>result: it doesn't seem to work still. >> >> (However, at one time about two >> weeks ago, while on the phone, I was able to surf the web >> with the NT server. In fact, I thought it worked. That was >> version 5.0b. Afterwards, when I turned on more than one >><bold> </bold>machine, it didn't work. An ascend tech support told me I need >> to wait for 5.1A for NAT for LAN. Now I have it, it still >> didn't work) In this scenario, however you would have a problem connecting to your ISP if you gave your Ascend an address of 200.200.200.200. Use NAT and assign your Pipe a secondary interface for NAT. >>Ascend claims that my ISP is at fault because they should not assign a >>static address to me but rather assign a dynamic one.... This doesn't matter. NAT works with both a static IP and a dynamic IP. >>So who is at fault? Are there anyways to rectify the situation? >>I am seriously considering dropping my ISP account to another provider or >>returning the P75 and get a Cisco 700 series... No one is to blame on this one...Maybe you should by a Farallon router if you are looking for something that is easy to configure and supports NAT also. ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request@bungi.com To get FAQ'd: <<A HREF="http://www.nealis.net/ascend/faq">http://www.nealis.net/ascend/faq</A>> </PRE> <!--X-MsgBody-End--> <!--X-Follow-Ups--> <!--X-Follow-Ups-End--> <!--X-References--> <HR> <STRONG>References</STRONG>: <UL> <LI><STRONG><A HREF="msg08676.html">Re: (ASCEND) Who's fault? P75 or my ISP. Cannot get on the Net.</A></STRONG></LI> <UL> <LI><EM>From</EM>: Joseph Bridgewater <you.dont@need.it.bungi.com></LI> </UL> </UL> <!--X-References-End--> <!--X-BotPNI--> <HR> <UL> <LI>Prev by Date: <STRONG><A HREF="msg08684.html">Re: (ASCEND) 5.1A for the Pipelines</A></STRONG> </LI> <LI>Next by Date: <STRONG><A HREF="msg08683.html">Re: (ASCEND) Keeping a p50 connected</A></STRONG> </LI> <LI>Prev by thread: <STRONG><A HREF="msg08676.html">Re: (ASCEND) Who's fault? P75 or my ISP. Cannot get on the Net.</A></STRONG> </LI> <LI>Next by thread: <STRONG><A HREF="msg08668.html">(ASCEND) Who's fault? P75 or my ISP. Cannot get on the Net.</A></STRONG> </LI> <LI>Index(es): <UL> <LI><A HREF="mail9.html#08690"><STRONG>Main</STRONG></A></LI> <LI><A HREF="thrd162.html#08690"><STRONG>Thread</STRONG></A></LI> </UL> </LI> </UL> <!--X-BotPNI-End--> <!--X-User-Footer--> <!--X-User-Footer-End--> </BODY> </HTML>