| » » » » proxy works fine, but LAN not in Neighborhood|
sipps Oct-20-00 01:56 AM
3 PCs, A, B, C on peer-peer; file/printer sharing enabled all three; A is set as a proxy server via cable modem; A and C recognize and mutually access; B appears in Neighborhood, although attempting to access renders error "incorrect name etc."; However, internet access available flawlessly on B (via proxy in A); Temporary fix is choosing protected device mode in IRQ steering of PCI Bus--B is available for indeteminate period thereafter on both A and C. I disabled some devices in config to see if IRQ conflicts with no success. Any ideas would be appreciated. Thanks.
1. RE: proxy works fine, but LAN not in Neighborhood
lbyard Oct-20-00 05:45 AM
In response to message 0
If B's motherboard has the VIA MVP3 chipset, download the 4-in-1 driver set and install the IRQ miniport driver. http://www.viatech.com/drivers/index.htm Larry
2. RE: proxy works fine, but LAN not in Neighborhood
sipps Oct-22-00 12:07 PM
In response to message 1
Thanks for your response.
The chipsets are Intel.
I'm using Win98 and when I reboot PC ('B' from original post) after adding Protected mode to IRQ steering for PCI bus (Device Manager, System), 'B' works fine on the LAN. However, during the reboot, the following screen appears:
"Cannot find a device file that may be needed to run Windows or a Windows app. The Windows registry or System.ini file refers to this device, but the device no longer exists.
...(either uninstall asso app or reinstall app)..."
then there are a number of ASCII characters.
Tried system file checker which found nothing.
Ideas on how to determine what file needs to be redressed?
3. RE: proxy works fine, but LAN not in Neighborhood
lbyard Oct-23-00 03:28 PM
In response to message 2
LAST EDITED ON Oct-23-00 AT 03:28 PM (GMT)
Try running msconfig and looking at the 386Enh section for a driver matching that in the error message and disabling it. Larry
4. RE: proxy works fine, but LAN not in Neighborhood
sipps Nov-15-00 01:42 AM
In response to message 3
Tried finding the problem driver in 386Enh and disabling it: actually disabled files one-by-one but to no avail. Have discovered, however, that changing the computer name and rebooting allows for access to computer "B". Once "B" is recognized and accessible, it works fine until rebooting it: rebooting the system without making any changes results in the same problem, i.e. "B" shows up in Network Neighborhood and Find Computer, but attempts to access "B" result in the error statement that the name is wrong and/or the computer is not accessible.
We did an over-the-top reinstall of WIN98 (not SE) and replaced the ethernet card with a different model: the same problem persists.
Any further ideas would be appreciated! Thanks!
5. RE: proxy works fine, but LAN not in Neighborhood
lbyard Nov-15-00 05:45 PM
In response to message 4
Gary, Usually those error messages include the name of the driver. It is somewhere… If you have the name, search the system.ini file and registry with regedit (Start, Run, regedit, Edit, Find). It can be caused by the incomplete installation of network components, especially dial-up networking (which you don’t need with a cable MODEM), and may be related to the other problem. Suggest uninstalling and reinstalling all network components, everything. You say “A is set as a proxy server via cable modem.” What software are you using for the proxy? That may be the problem… Larry
6. RE: proxy works fine, but LAN not in Neighborhood
sipps Nov-15-00 11:46 PM
In response to message 5
Thanks for your (quick) response. I followed your suggestion and found a file, NDISFILT.VXD, in the registry. This is a Norton Internet Security file. It appeared in a fatal exception error when I attempted to REMOVE the Network Adapter from the Device Manager. I had originally had this package installed on this PC but uninstalled it because I decided to make another PC on the network the proxy server. I bought Norton AntiVirus 2000 and installed it on the "problem PC." From what I can tell, the file NDISFILT.VXD is not part of the AntiVirus 2000 package. Is it possible that this file is a vestige of the Internet Security Suite that somehow was not removed during the uninstall? I tried looking at Symantec's website and have yet to find any info.
I appreciate any ideas you have.
7. RE: proxy works fine, but LAN not in Neighborhood
mhindle Nov-16-00 03:04 PM
In response to message 6
do you run atguard software. It can cause heaps of conflicts with your networking software and give you gpfs for this NDISFILT.VXD
8. RE: proxy works fine, but LAN not in Neighborhood
lbyard Nov-16-00 06:06 PM
In response to message 6
Yes, some program uninstalls may leave stuff behind like that. Also, an aborted or improper uninstall can cause problems. I would backup the registry and delete the entry. Larry
9. RE: proxy works fine, but LAN not in Neighborhood
sipps Nov-17-00 02:24 AM
In response to message 8
There were MANY files from Norton Internet Security Suite although I had uninstalled it: I tried to uninstall it again, but the Windows Uninstall indicated necessary files were missing. So, I reinstalled NISS and then uninstalled it successfully. I also uninstalled Norton Antivirus 2000 which I had installed after I had originally uninstalled (or, so I thought) NISS. After the unstalls, the NDISFILT.VXD registry entry was gone. I reinstalled the ethernet card, configured, and the LAN appears to be working like a charm!
Thanks for the idea and the encouragement that we were dealing with a software problem.
Guides | How to |
Online Store |
Forums | Forum
| Links |
News | Newsletter |
About Dux |
Advertising | Contact Info |