Re: (ASCEND) 6.1.0 and Winsock.dll (version 2.0) (fwd)

[Eric Hunter <ehunter@netrover.com>]

At 11:56 PM 6/2/98 +0100, Leland E. Vandervort wrote:
>
>If this winsock problem is as accurate as people are saying it is (which
I'm not
>so sure since we've had no reports of a problem and now going on day 3 since
>upgrading), doesn't it make more sense for Ascend to fix the bug in the
max/tnt
>software rather than each of us getting a couple thousand customers to fix
their
>win95 tcp stack ?

If its only specific versions of Winsock 2 stacks that have problems, this
suggests its a Microsoft bug.  Very few users will actually be using
Winsock 2 anyways.  Only the ones that have a need to 'nuke' people it
seems.  Other than that, there is no real benefit to install Winsock 2.
Windows 98 isn't affected by this (Which has Winsock 2)


 Eric

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

---

Follow-Ups:

• (ASCEND) RFC ASCEND VPN solution?
• From: dreamwvr <dreamwvr@dreamwvr.com>

References:

• Re: (ASCEND) 6.1.0 and Winsock.dll (version 2.0) (fwd)
• From: "Leland E. Vandervort" <lelandv@innotts.co.uk>

---

• Prev by Date: Re: (ASCEND) [Q] DSLPipe S as COE and CPE ?
• Next by Date: Re: (ASCEND) Dynamic ip on a pipe 15, or 25
• Prev by thread: Re: (ASCEND) 6.1.0 and Winsock.dll (version 2.0) (fwd)
• Next by thread: (ASCEND) RFC ASCEND VPN solution?
• Index(es):
  • Main
  • Thread