No, you just run dhcp.client and if you have a dhcp server on your network,
it will give you an IP address.


On 10-05-14 3:23 PM, "Julian Babel" <community-noreply@qnx.com> wrote:

> Have any links that can show me more about using dhcp.client?  I have to
> admit, my knowledge in that is lacking.
> 
> 
> 
> _______________________________________________
> 
> QNX4 Community Support
> http://community.qnx.com/sf/go/post54764
> 

-- 
Hugh Brown                      (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd.        (613) 591-3579           (fax)
175 Terence Matthews Cres.       email:  hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
 

There is a TCPIP 5.0 update on our web, but I don't know whether this will
solve your problem, as I don't know what you are trying to achieve.


On 10-05-14 4:00 PM, "Julian Babel" <community-noreply@qnx.com> wrote:

> hrmm..well I just tried that and it doesn't seem like the IP address is the
> issue.  I typed sin and realized that Socket is also listed as being
> initialized.  You don't think this isn't an issue that I have closed sockets?
> I looked within tcpip and sysinit and both look fine.  I'm just curious...the
> new version, 2009 (which i do have installed) included all the latest and
> greatest from the tcp/ip configuration?
> 
> 
> 
> _______________________________________________
> 
> QNX4 Community Support
> http://community.qnx.com/sf/go/post54768
> 

-- 
Hugh Brown                      (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd.        (613) 591-3579           (fax)
175 Terence Matthews Cres.       email:  hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
 

If you ping 192.168.1.30, you are pinging yourself, so this will work. How
are you connecting to the external hard disk? Is it via a switch or a direct
cable? If it is a direct cable, it it a crossover cable? Can you connect to
your internal network and ping other machines?


On 10-05-17 8:41 AM, "Julian Babel" <community-noreply@qnx.com> wrote:

> Good Morning Mr. Brown,
>    
>   I apologize if my objective seemed unclear.  Basically, i've configured
> several qnx systems for my workplace using QNX 4.  I've always had an issue
> with establishing the networks on them in recent months due to the failing
> disk drives that enable the tcp/ip configuration.  I managed to override this
> by using digi card drivers and previous configuration setups on pre-existing
> machines.  Currently, the new box that I have been instructed to set up MUST
> have ethernet capabilities.  We are getting rid of Digi.  I have no disk
> drive, but luckily QNX released their 2009 cd patch that cleared the majority
> of my previous hardware woes.  The only exception seems to be this networking
> issue.  
> 
> In the initialization of my setup, I enabled a TCP/IP connection and set the
> node to 30, enabling my network, I assume, to be 192.168.1.30.  When I ping
> this, I get a successful ping.  However, I wanted to test this on an outside
> network, so I attached a network enabled WD external harddrive, plugging in
> the ethernet cable, tried to ping (eg 192.168.1.50) and am unable to get a
> pulse.  This is where my confusion seems to manifest.
> 
> Your advice on loading the drivers was excellent, however, under your
> guidance, you were right in assuming that the drivers seem to already be
> active and functioning, which is why I keep getting the "error" messages (plus
> when you instructed to use 'sin', I saw this as well).
> 
> So right now, my problem seems to be getting that outside connection to work.
> I'm currently looking at old files from previous qnx machines that were digi
> enabled to see what the missing link was.  I'm not too sure what else I may be
> able to do though.
> 
> I appreciate that time you've taken so far to help me with this. Does this
> clarify things a bit?
> 
> 
> 
> _______________________________________________
> 
> QNX4 Community Support
> http://community.qnx.com/sf/go/post54834
> 

-- 
Hugh Brown                      (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd.        (613) 591-3579           (fax)
175 Terence Matthews Cres.       email:  hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
 

If you look at the output from 'netinfo -L1', does the Media Rate line show
a speed? If not, then that is why you cannot communicate. Try connecting via
a switch.


On 10-05-17 10:01 AM, "Julian Babel" <community-noreply@qnx.com> wrote:

> Oh. Interesting.  It looks like I am not connected.  No packets are being
> transmitted/received.  And en1 has that interface.
> 
> 
> 
> _______________________________________________
> 
> QNX4 Community Support
> http://community.qnx.com/sf/go/post54851
> 

-- 
Hugh Brown                      (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd.        (613) 591-3579           (fax)
175 Terence Matthews Cres.       email:  hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
 

1000Mb/s HDX is an invalid duplex for gigabit. Gigabit should only work at
1000Mb/s FDX. I suggest you try a switch.


On 10-05-17 10:23 AM, "Julian Babel" <community-noreply@qnx.com> wrote:

> It shows 1000Mb/s HDX.
> 
> 
> 
> _______________________________________________
> 
> QNX4 Community Support
> http://community.qnx.com/sf/go/post54856
> 

-- 
Hugh Brown                      (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd.        (613) 591-3579           (fax)
175 Terence Matthews Cres.       email:  hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
 

Does the hard disk work on another machine with the same IP address?


On 10-05-17 10:47 AM, "Julian Babel" <community-noreply@qnx.com> wrote:

> Ok, so I tried just setting up a local hub.  Used a switch to connect to the
> qnx box and have a connection from the harddrive to the switch and reset.
> Still not getting anything.
> 
> 
> 
> _______________________________________________
> 
> QNX4 Community Support
> http://community.qnx.com/sf/go/post54858
> 

-- 
Hugh Brown                      (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd.        (613) 591-3579           (fax)
175 Terence Matthews Cres.       email:  hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
 

Good Grief,
  I figured out the problem.  I hardcoded a minor change within the sysinit file.  However, the main problem as 
embarrasing to admit, was that the IP address was being read from the ethernet port in the pci slot and not the 
motherboard as I had the cable plugged into the entire time.  As much as I was switching cables about, I neglected the 
one from the driver..so quick switch...worked.

Well..back to EE 101.  Thanks for all your help and patience Mr. Brown.