network connection problems

Greetings all,
Here’s my problem…
Our company currently uses QNX 4.0 for our retail custom software package.
My supervisor asked me to investigate the possibility of using Neutrino as a
platform instead and I have been doing some beta testing.

One really big problem: I can’t connect to the network.
First of all, my network card is working ok under a windows environment, so
it is not a bad card…
My machine has a 3com 905 card supporting UTP, and is recognized by the
nettrap and io-net commands. Neutrino names it en0, as it should. I have
entered all of the LAN addressing as per our network administrator, but I
still cannot connect to anything. I know that there is some connection that
is established, because before configuring the card, a ping command to the
proxy server results in “no route to host”. After configuring, I can ping
the proxy server, but I get “host is down”. The proxy server is in fact not
down, as I can ping it sucessfully from my other machine running QNX 4.0

I have tried a plethora of options retrieved from the QNX helpviewer and
from the QNX knowledge base and from the QNX newsgroups, but still no
success. Could someone please lend a hand? I will be happy to provide any
additional information should you need it.

Thanks in advance,

Daniel Ahrens

On Thu, 3 May 2001 11:35:58 -0400, “Daniel Ahrens”
<danielahrens@fortna.com> wrote:

Run nicinfo to see if you are receiving packet.

Lots of people have trouble with 905 card, try a different model.

Greetings all,
Here’s my problem…
Our company currently uses QNX 4.0 for our retail custom software package.
My supervisor asked me to investigate the possibility of using Neutrino as a
platform instead and I have been doing some beta testing.

One really big problem: I can’t connect to the network.
First of all, my network card is working ok under a windows environment, so
it is not a bad card…
My machine has a 3com 905 card supporting UTP, and is recognized by the
nettrap and io-net commands. Neutrino names it en0, as it should. I have
entered all of the LAN addressing as per our network administrator, but I
still cannot connect to anything. I know that there is some connection that
is established, because before configuring the card, a ping command to the
proxy server results in “no route to host”. After configuring, I can ping
the proxy server, but I get “host is down”. The proxy server is in fact not
down, as I can ping it sucessfully from my other machine running QNX 4.0

I have tried a plethora of options retrieved from the QNX helpviewer and
from the QNX knowledge base and from the QNX newsgroups, but still no
success. Could someone please lend a hand? I will be happy to provide any
additional information should you need it.

Thanks in advance,

Daniel Ahrens

Hi Daniel,

Could you post the full model number of the 905 adapter, and the output from ‘pci -v’.
Also, how are you starting the driver (command line).

Regards,
Joe

Daniel Ahrens <danielahrens@fortna.com> wrote:

Greetings all,
Here’s my problem…
Our company currently uses QNX 4.0 for our retail custom software package.
My supervisor asked me to investigate the possibility of using Neutrino as a
platform instead and I have been doing some beta testing.

One really big problem: I can’t connect to the network.
First of all, my network card is working ok under a windows environment, so
it is not a bad card…
My machine has a 3com 905 card supporting UTP, and is recognized by the
nettrap and io-net commands. Neutrino names it en0, as it should. I have
entered all of the LAN addressing as per our network administrator, but I
still cannot connect to anything. I know that there is some connection that
is established, because before configuring the card, a ping command to the
proxy server results in “no route to host”. After configuring, I can ping
the proxy server, but I get “host is down”. The proxy server is in fact not
down, as I can ping it sucessfully from my other machine running QNX 4.0

I have tried a plethora of options retrieved from the QNX helpviewer and
from the QNX knowledge base and from the QNX newsgroups, but still no
success. Could someone please lend a hand? I will be happy to provide any
additional information should you need it.

Thanks in advance,

Daniel Ahrens

Joe,

Here is the info you requested:

Model Number - 3com 905C-TX
Command Line - ’ io-net -del900 -pttcpip’
After I start the network card, I use the network config dialog box in
photon to set my local ip address and netmask.
Are there any other settings that I should be giving attention to? My
network administrator says no, and that it should autodetect.
I also set the hostname under the network tab to a unique name for my pc
and the domain name to our corporate network. Everything
else I left blank. Is this right?

At the end of this message I have posted my pci -v output.

Thanks for your help,

Daniel


“Hardware Support Account” <hw@qnx.com> wrote in message
news:9cs412$2ip$1@nntp.qnx.com

Hi Daniel,

Could you post the full model number of the 905 adapter, and the output
from ‘pci -v’.
Also, how are you starting the driver (command line).

Regards,
Joe

Daniel Ahrens <> danielahrens@fortna.com> > wrote:
Greetings all,
Here’s my problem…
Our company currently uses QNX 4.0 for our retail custom software
package.
My supervisor asked me to investigate the possibility of using Neutrino
as a
platform instead and I have been doing some beta testing.

One really big problem: I can’t connect to the network.
First of all, my network card is working ok under a windows environment,
so
it is not a bad card…
My machine has a 3com 905 card supporting UTP, and is recognized by the
nettrap and io-net commands. Neutrino names it en0, as it should. I have
entered all of the LAN addressing as per our network administrator, but
I
still cannot connect to anything. I know that there is some connection
that
is established, because before configuring the card, a ping command to
the
proxy server results in “no route to host”. After configuring, I can
ping
the proxy server, but I get “host is down”. The proxy server is in fact
not
down, as I can ping it sucessfully from my other machine running QNX 4.0

I have tried a plethora of options retrieved from the QNX helpviewer and
from the QNX knowledge base and from the QNX newsgroups, but still no
success. Could someone please lend a hand? I will be happy to provide
any
additional information should you need it.

Thanks in advance,

Daniel Ahrens

PCI version = 2.10

Class = Bridge (Host/PCI)
Vendor ID = 8086h, Intel Corporation
Device ID = 1130h, 82815 Host-Hub Interface Bridge / DRAM Ctrlr
PCI index = 0h
Class Codes = 060000h
Revision ID = 2h
Bus number = 0
Device number = 0
Function num = 0
Status Reg = 2090h
Command Reg = 106h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0
Capabilities Pointer = 88h
Capability ID = 9h
Capabilities = f104h - 0h
Capability ID = 2h
Capabilities = 20h - 1f000207h

Class = Bridge (PCI/PCI)
Vendor ID = 8086h, Intel Corporation
Device ID = 1131h, 82815 AGP Bridge
PCI index = 0h
Class Codes = 060400h
Revision ID = 2h
Bus number = 0
Device number = 1
Function num = 0
Status Reg = 20h
Command Reg = 107h
Header type = 1h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
Primary Bus Number = 0h
Secondary Bus Number = 1h
Subordinate Bus Number = 1h
Secondary Latency Timer = 40h
I/O Base = c0h
I/O Limit = c0h
Secondary Status = 22a0h
Memory Base = ff80h
Memory Limit = ff80h
Prefetchable Memory Base = ee90h
Prefetchable Memory Limit= f690h
Prefetchable Base Upper 32 Bits = 0h
Prefetchable Limit Upper 32 Bits = 0h
I/O Base Upper 16 Bits = ffffh
I/O Limit Upper 16 Bits = ffffh
Bridge Control = 8ns
PCI Int Pin = NC
Interrupt line = 0

Class = Bridge (PCI/PCI)
Vendor ID = 8086h, Intel Corporation
Device ID = 244eh, 82801BA Hub Interface to PCI Bridge
PCI index = 0h
Class Codes = 060400h
Revision ID = 2h
Bus number = 0
Device number = 30
Function num = 0
Status Reg = 80h
Command Reg = 107h
Header type = 1h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
Primary Bus Number = 0h
Secondary Bus Number = 2h
Subordinate Bus Number = 2h
Secondary Latency Timer = 40h
I/O Base = d0h
I/O Limit = d0h
Secondary Status = 2280h
Memory Base = ff90h
Memory Limit = ff90h
Prefetchable Memory Base = f6a0h
Prefetchable Memory Limit= f6a0h
Prefetchable Base Upper 32 Bits = 0h
Prefetchable Limit Upper 32 Bits = 0h
I/O Base Upper 16 Bits = ffffh
I/O Limit Upper 16 Bits = ffffh
Bridge Control = 2ns
PCI Int Pin = NC
Interrupt line = 0

Class = Bridge (PCI/ISA)
Vendor ID = 8086h, Intel Corporation
Device ID = 2440h, 82801BA LPC Interface Bridge
PCI index = 0h
Class Codes = 060100h
Revision ID = 2h
Bus number = 0
Device number = 31
Function num = 0
Status Reg = 280h
Command Reg = 10fh
Header type = 0h Multi-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0

Class = Mass Storage (IDE)
Vendor ID = 8086h, Intel Corporation
Device ID = 244bh, 82801BA IDE Controller
PCI index = 0h
Class Codes = 010180h
Revision ID = 2h
Bus number = 0
Device number = 31
Function num = 1
Status Reg = 280h
Command Reg = 5h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
IO Address = ffa0h length 16 enabled
Subsystem Vendor ID = 8086h
Subsystem ID = 4541h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 2442h, 82801BA USB Controller
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 2h
Bus number = 0
Device number = 31
Function num = 2
Status Reg = 280h
Command Reg = 5h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
IO Address = ef80h length 32 enabled
Subsystem Vendor ID = 8086h
Subsystem ID = 4541h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 10

Class = Serial Bus (SMBus)
Vendor ID = 8086h, Intel Corporation
Device ID = 2443h, 82801BA SMBus Controller
PCI index = 0h
Class Codes = 0c0500h
Revision ID = 2h
Bus number = 0
Device number = 31
Function num = 3
Status Reg = 280h
Command Reg = 1h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
IO Address = efa0h length 16 enabled
Subsystem Vendor ID = 8086h
Subsystem ID = 4541h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT B
Interrupt line = 9

Class = Display (VGA)
Vendor ID = 1002h, ATI Technologies
Device ID = 5046h, Rage Fury MAXX AGP4x
PCI index = 0h
Class Codes = 030000h
Revision ID = 0h
Bus number = 1
Device number = 0
Function num = 0
Status Reg = 2b0h
Command Reg = 87h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 8h un-cacheable
Mem Address = f0000000h prefetchable 32bit length 67108864 enabled
IO Address = c800h length 256 enabled
Mem Address = ff8fc000h 32bit length 16384 enabled
Subsystem Vendor ID = 1002h
Subsystem ID = 404h
Expansion ROM = ff8c0000h length 131072 disabled
Max Lat = 0ns
Min Gnt = 8ns
PCI Int Pin = INT A
Interrupt line = 11
Capabilities Pointer = 50h
Capability ID = 2h
Capabilities = 20h - 1f000207h
Capability ID = 1h
Capabilities = 202h - 0h

Class = Network (Ethernet)
Vendor ID = 10b7h, 3Com Corporation
Device ID = 9200h, 3C905C-TX Fast EtherLink for PC Management NIC
PCI index = 0h
Class Codes = 020000h
Revision ID = 78h
Bus number = 2
Device number = 9
Function num = 0
Status Reg = 210h
Command Reg = 117h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 8h un-cacheable
IO Address = dc00h length 128 enabled
Mem Address = ff9ffc00h 32bit length 128 enabled
Subsystem Vendor ID = 10b7h
Subsystem ID = 1000h
Expansion ROM = ff9c0000h length 131072 disabled
Max Lat = 10ns
Min Gnt = 10ns
PCI Int Pin = INT A
Interrupt line = 3
Capabilities Pointer = dch
Capability ID = 1h
Capabilities = fe02h - b7004100h

Class = Multimedia (Audio)
Vendor ID = 1274h, Ensoniq
Device ID = 1371h, ES1371 AudioPCI
PCI index = 0h
Class Codes = 040100h
Revision ID = 8h
Bus number = 2
Device number = 11
Function num = 0
Status Reg = 410h
Command Reg = 105h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
IO Address = df00h length 64 enabled
Subsystem Vendor ID = 1274h
Subsystem ID = 1371h
Max Lat = 128ns
Min Gnt = 12ns
PCI Int Pin = INT A
Interrupt line = 11
Capabilities Pointer = dch
Capability ID = 1h
Capabilities = 421h - 3h

Joe,

Since my last post I have tried a number of different network cards, and
some have worked, so I know that my 3com problem is not network based or
tcp/ip protocol based, and as I mentioned in my first posting, the 3com card
works fine in QNX 4 and Windows environments.

It is important for me to get the 3com card working, as most of the pc’s
that we have out in the field (where we may be upgrading to QNX 6) have 3com
cards, and my supervisor is not looking to replace all of them! :slight_smile:

Thanks again,

Daniel

“Hardware Support Account” <hw@qnx.com> wrote in message
news:9cs412$2ip$1@nntp.qnx.com

Hi Daniel,

Could you post the full model number of the 905 adapter, and the output
from ‘pci -v’.
Also, how are you starting the driver (command line).

Regards,
Joe

Daniel Ahrens <> danielahrens@fortna.com> > wrote:
Greetings all,
Here’s my problem…
Our company currently uses QNX 4.0 for our retail custom software
package.
My supervisor asked me to investigate the possibility of using Neutrino
as a
platform instead and I have been doing some beta testing.

One really big problem: I can’t connect to the network.
First of all, my network card is working ok under a windows environment,
so
it is not a bad card…
My machine has a 3com 905 card supporting UTP, and is recognized by the
nettrap and io-net commands. Neutrino names it en0, as it should. I have
entered all of the LAN addressing as per our network administrator, but
I
still cannot connect to anything. I know that there is some connection
that
is established, because before configuring the card, a ping command to
the
proxy server results in “no route to host”. After configuring, I can
ping
the proxy server, but I get “host is down”. The proxy server is in fact
not
down, as I can ping it sucessfully from my other machine running QNX 4.0

I have tried a plethora of options retrieved from the QNX helpviewer and
from the QNX knowledge base and from the QNX newsgroups, but still no
success. Could someone please lend a hand? I will be happy to provide
any
additional information should you need it.

Thanks in advance,

Daniel Ahrens

Hi Daniel,

From the output of pci -vvv it looks like the 3Com card is the new
905CX-TX, as the output of pci shows a rev of 0x78. This adapter
needs the latest driver, which hasn’t shipped yet.

Just to make sure though, could you run nicinfo, once you have the
network driver running and the network configured.

Thanks

Erick.


Daniel Ahrens <danielahrens@fortna.com> wrote:

Joe,

Since my last post I have tried a number of different network cards, and
some have worked, so I know that my 3com problem is not network based or
tcp/ip protocol based, and as I mentioned in my first posting, the 3com card
works fine in QNX 4 and Windows environments.

It is important for me to get the 3com card working, as most of the pc’s
that we have out in the field (where we may be upgrading to QNX 6) have 3com
cards, and my supervisor is not looking to replace all of them! > :slight_smile:

Thanks again,

Daniel

“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9cs412$2ip$> 1@nntp.qnx.com> …
Hi Daniel,

Could you post the full model number of the 905 adapter, and the output
from ‘pci -v’.
Also, how are you starting the driver (command line).

Regards,
Joe

Daniel Ahrens <> danielahrens@fortna.com> > wrote:
Greetings all,
Here’s my problem…
Our company currently uses QNX 4.0 for our retail custom software
package.
My supervisor asked me to investigate the possibility of using Neutrino
as a
platform instead and I have been doing some beta testing.

One really big problem: I can’t connect to the network.
First of all, my network card is working ok under a windows environment,
so
it is not a bad card…
My machine has a 3com 905 card supporting UTP, and is recognized by the
nettrap and io-net commands. Neutrino names it en0, as it should. I have
entered all of the LAN addressing as per our network administrator, but
I
still cannot connect to anything. I know that there is some connection
that
is established, because before configuring the card, a ping command to
the
proxy server results in “no route to host”. After configuring, I can
ping
the proxy server, but I get “host is down”. The proxy server is in fact
not
down, as I can ping it sucessfully from my other machine running QNX 4.0

I have tried a plethora of options retrieved from the QNX helpviewer and
from the QNX knowledge base and from the QNX newsgroups, but still no
success. Could someone please lend a hand? I will be happy to provide
any
additional information should you need it.

Thanks in advance,

Daniel Ahrens

Hi Erick,

I was away on business and wasn’t able to perform the tests that you asked
for until this afternoon. Sorry.
Here is the requested output:

3COM (90xC) 10BASE-T/100BASE-TX Ethernet Controller
Physical Node ID … ADAD00 000000
Current Physical Node ID … ADAD00 000000
Media Rate … 0 kb/s half-duplex UTP
MTU … 1514
Lan … 0
I/O Port Range … 0xDC00 → 0xDC7F
Hardware Interrupt … 0x3

Total Packets Txd OK … 0
Total Packets Txd Bad … 0
Total Packets Rxd OK … 0
Total Rx Errors … 0

Tx Collision Errors … 0
Tx Collisions Errors (aborted) … 0
Carrier Sense Lost on Tx … 0
FIFO Underruns During Tx … 0
Tx defered … 0
Out of Window Collisions … 0
FIFO Overruns During Rx … 0
Alignment errors … 0
CRC errors … 0

Thanks,

Daniel


“Hardware Support Account” <hw@qnx.com> wrote in message
news:9cut2j$npc$1@nntp.qnx.com

Hi Daniel,

From the output of pci -vvv it looks like the 3Com card is the new
905CX-TX, as the output of pci shows a rev of 0x78. This adapter
needs the latest driver, which hasn’t shipped yet.

Just to make sure though, could you run nicinfo, once you have the
network driver running and the network configured.

Thanks

Erick.


Daniel Ahrens <> danielahrens@fortna.com> > wrote:
Joe,

Since my last post I have tried a number of different network cards, and
some have worked, so I know that my 3com problem is not network based or
tcp/ip protocol based, and as I mentioned in my first posting, the 3com
card
works fine in QNX 4 and Windows environments.

It is important for me to get the 3com card working, as most of the pc’s
that we have out in the field (where we may be upgrading to QNX 6) have
3com
cards, and my supervisor is not looking to replace all of them! > :slight_smile:

Thanks again,

Daniel

“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9cs412$2ip$> 1@nntp.qnx.com> …
Hi Daniel,

Could you post the full model number of the 905 adapter, and the output
from ‘pci -v’.
Also, how are you starting the driver (command line).

Regards,
Joe

Daniel Ahrens <> danielahrens@fortna.com> > wrote:
Greetings all,
Here’s my problem…
Our company currently uses QNX 4.0 for our retail custom software
package.
My supervisor asked me to investigate the possibility of using
Neutrino
as a
platform instead and I have been doing some beta testing.

One really big problem: I can’t connect to the network.
First of all, my network card is working ok under a windows
environment,
so
it is not a bad card…
My machine has a 3com 905 card supporting UTP, and is recognized by
the
nettrap and io-net commands. Neutrino names it en0, as it should. I
have
entered all of the LAN addressing as per our network administrator,
but
I
still cannot connect to anything. I know that there is some
connection
that
is established, because before configuring the card, a ping command
to
the
proxy server results in “no route to host”. After configuring, I can
ping
the proxy server, but I get “host is down”. The proxy server is in
fact
not
down, as I can ping it sucessfully from my other machine running QNX
4.0

I have tried a plethora of options retrieved from the QNX helpviewer
and
from the QNX knowledge base and from the QNX newsgroups, but still no
success. Could someone please lend a hand? I will be happy to provide
any
additional information should you need it.

Thanks in advance,

Daniel Ahrens
\