SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 12 | March | 2006 ]

>> Next Message >>


Date: Sun, 12 Mar 2006 06:37:39 PST8
From: Harry Motin <hmotin@sbcglobal.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Network Not Working


Content Type: text/plain

Content-Transfer-Encoding: 8bit

Hello Everyone:
Here is some more information on my network difficulties. In an effort to isolate the problem I did the following things, in order:

1. Deleted the Intel NIC adapter from MPTS (it now specifies only the VIA NIC, built into the motherboard)

2. Read the LANTRAN.LOG file. It said the following:
"Multiple adapters are trying to use the same interrupt level. Request to bind VECTOR to FETND_NIF cannot be completed"

3. According to my system information the VIA adapter, the video AGP adapter and the Adaptec SCSI adapter were all sharing interrupt A (hex). I was able to remove the video AGP adapter from this interrupt level by altering a BIOS setting, but that was all. I could not effect either the VIA adaptetr or the Adaptec adapter in the BIOS.

Questions:
1. Is the only fix for this to move the Adaptec SCSI adapter to a different PCI slot? Will that work?

2. Can anyone explain the message about binding "VECTOR to FETND_NIF"? What is VECTOR? I know that FETND_NIF is the driver for the VIA NIC.

Thanks for any help on this.
HCM

Harry Motin wrote:
Hello Everyone:
I need some help reestablishing my network on my new motherboard. What's different is that I now have 2 NEW network cards on the board. I have an Intel Pro 10/100 and a VIA 10/100 from the motherboard. I do not have any network connections on either card. Neither card can see my DHCP server, which is my router. When I boot up there is a long wait at a particular point and I'm pretty sure that my system is waiting to receive a dynamic IP address. The dynamic assignment fails and the system continues the boot.

It looks to me as though the drivers are not binding to the Intel adapter, but they are binding to the VIA adapter (I think). When I try to ping a known and internal IP address on my system, I get a message that the ping failed because a route has not been established.

I really do not know how to start troubleshooting this problem. Any help on this is greatly appreciated. Thanks in advance.

HCM


Content Type: text/html

Content-Transfer-Encoding: 8bit

Hello Everyone:
Here is some more information on my network difficulties. In an effort to isolate the problem I did the following things, in order:
 
1.  Deleted the Intel NIC adapter from MPTS (it now specifies only the VIA NIC, built into the motherboard)
 
2.  Read the LANTRAN.LOG file. It said the following:
"Multiple adapters are trying to use the same interrupt level. Request to bind VECTOR to FETND_NIF cannot be completed"
 
3.  According to my system information the VIA adapter, the video AGP adapter and the Adaptec SCSI adapter were all sharing interrupt A (hex). I was able to remove the video AGP adapter from this interrupt level by altering a BIOS setting, but that was all. I could not effect either the VIA adaptetr or the Adaptec adapter in the BIOS.
 
Questions:
1.  Is the only fix for this to move the Adaptec SCSI adapter to a different PCI slot? Will that work?
 
2.  Can anyone explain the message about binding "VECTOR to FETND_NIF"? What is VECTOR? I know that FETND_NIF is the driver for the VIA NIC.
 
Thanks for any help on this.
HCM


Harry Motin <hmotin@sbcglobal.net> wrote:
Hello Everyone:
I need some help reestablishing my network on my new motherboard. What's different is that I now have 2 NEW network cards on the board. I have an Intel Pro 10/100 and a VIA 10/100 from the motherboard. I do not have any network connections on either card. Neither card can see my DHCP server, which is my router. When I boot up there is a long wait at a particular point and I'm pretty sure that my system is waiting to receive a dynamic IP address. The dynamic assignment fails and the system continues the boot.
 
It looks to me as though the drivers are not binding to the Intel adapter, but they are binding to the VIA adapter (I think). When I try to ping a known and internal IP address on my system, I get a message that the ping failed because a route has not been established.
 
I really do not know how to start troubleshooting this problem. Any help on this is greatly appreciated. Thanks in advance.
 
HCM


>> Next Message >>

Return to [ 12 | March | 2006 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.