To resolve it, go to the MicroSoft site and download all the security
fixes you can find for Win95. Do this to one machine at a time.
You may want to also add some filters to your router, one would be to
block all udp to ports 137,138,139.
You can always put a better OS on your machines :-)
K
On Fri, 17 Jul 1998, CAFENET wrote:
> Greetings.....
>
> As of last night, our system went down, and the problem seems to be
> with
> our Portmaster Synchronous Office Router. Unfortunately, I'm not nearly
> enough
> of a techie to know what to do about it. The guy that I've hired as my
> technical
> assistant is stumped as well (and he only speaks Spanish, which is why
> I'm the
> one writing this letter), and my ISP tech support people have been
> completely
> and totally useless to me, despite the fact that the ISP owns the
> router.
> Anyway, here is the situation. We have 128Kbps fiberoptic coming
> into a
> 2603 Mainstreet DTU modem. From there it goes to our Portmaster, and
> from
> there to a recently changed 3Com Superstack hub. (The problem occurs
> with both the old and the new hubs.) From there, the signal goes into
> our
> server, which is running Windows NT. However, I should note that when
> the
> server is turned off, and the signal runs directly from the hub to the
> workstations,
> the problem persists. This is one reason that we suspect the router.
> We have 13 workstations running Windows 95. As of last night, one
> by
> one the workstations went to the blue Win95 error screen, and the error
> was
> "An exception OE has occurred at 0028:C1021956 in VXD MSTCP (01) +
> 0000414E. This was called from 0028:C00:C0045648 iin VXD NDIS (01) +.
> Press any key to continue, yadda yadda yadda." Today, the problem is
> still there.
> Strangely enough, the only machine that has been immune to this problem
> is the
> one that we have attached to the proxy server. It has never received
> the error
> message. Meanwhile, we are a cybercafe that is losing a great deal of
> money
> due to not being able to connect to the internet.
> When the error message occurs, we have to power down the
> workstation.
> Then we turn the power on again, and the system is connected to the
> internet
> again, and it works for an average of five minutes, until the error
> occurs again.
> I'm currently in the process of doing a web search for good
> information,
> troubleshooting software, or whatever I can find. However, in the
> interest
> of getting the problem solved as quickly as possible, I'm also throwing
> the
> problem onto this list. Does anyone have any idea what I need to do, or
>
> where (specifically) I can find the solution?
>
> Thank you very much,
> Bryan Short,
> Cafe Net Cybercafe,
> Quito, Ecuador
>
>
> -
> To unsubscribe, email 'majordomo@livingston.com' with
> 'unsubscribe portmaster-users' in the body of the message.
> Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>
>
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>