(ASCEND) Windows/Unix Ping and Pipelines

[vendramin@niia.net]

I noticed that there has been some discussions lately on Windows
login timeouts. Here is an interesting problem we are currently 
having.

There are three Pipeline 130's. One connected to the remote end
of our POP (point B). Another at that same location connected to
a T1 (point B again) that routes back to another location (point C). 
Let's say the POP is point A. The two at point B are connected by
your typical 10BaseT/ethernet network.

All of our Unix hosts at our main location can ping any of the Pipelines
(or for that matter any host on their network). Same with using the 
ping command from within the Pipelines or Ciscos - no problems. Yet, any
of our Microsoft hosts fail to ping. All of the ping requests come back
"request timeout". The Microsoft OS does not matter. Same result.

Have any of you seen anything like this?

Thanks.


Bill Vendramin
Operations Manager
Northern Indiana Internet Access, Inc.
vendramin@niia.net


++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>

---

• Prev by Date: (ASCEND) Re: Ticket # 240400
• Next by Date: Re: (ASCEND) MaxTNT 2.1
• Prev by thread: (ASCEND) max 4000 query
• Next by thread: Re: (ASCEND) Windows/Unix Ping and Pipelines
• Index(es):
  • Main
  • Thread