Dream Machine ( Build your own PC ) Message Board

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Dream Machine ( Build your own PC )

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: Spots who wrote (6288)	2/15/1999 8:41:00 AM
From: Sean W. Smith	Read Replies (1) of 14778

Spots, Two things here.... 1. Did you ping yourself by IP address??? Chances are this would have died with Bad IP address this points to the #2. 2. If your familar with NDIS configuration files look at the protocol.ini file. Almost always the culprit is in there. I can usually fix them by hand as I understand NDIS configs my test lab days at IBM. EDIT: SPX implies SP3 or SP4 not the network protocol. The easy solution to this is. Uninstall all networking components reboot. Apply SPX and reboot. re-install network and SPX. You never mentioned what SP Level. Again realize that ANYTIME A file is copied from the NT CD (as with most network changes), service packs must be re-applied or strange things will happen. seen it many many times.... Sean

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next