Socket: Network is down

I've installed Warp 4 (with FP 4) and get a "Socket: Network is down" error when booting.  This is before the PM starts up.  I hit return and
the boot continues and all my networking seems to be fine.
All tcpip services function properly and I'm able to logon
using Netware.  I've installed IBM tcpip and the netware requester.  Maybe I've installed a protocol that isn't present on our network?  Netstat -s appears normal.
sfahey103197Asked:
Who is Participating?
 
sbuftonConnect With a Mentor Commented:
Take a look in the TCP/IP configuration - check which services you are starting. Also check which network cards are activated - it may be that you have enabled a network card number which does not exist in MPTS.

If you have NetBIOS over TCP/IP enabled, check in MPTS to see whether you have configured NetBIOS Socket access - perhaps there is something wrongly set up there.

0
 
DargonCommented:
Check your startup.cmd and Startup folder
to see if you are starting and TCP/IP
programs at boot time before "TCP/IP
Startup" in the Startup folder has a
chance to run.  Also, is the message you
receive a PM message box or does it appear
before the switch to PM.  If it's a PM
box, does the title bar give a clue as to
who is reporting the error?  If it is
before the switch to PM, what is printed
right before and right after the message?
0
 
sfahey103197Author Commented:
Edited text of question
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
sfahey103197Author Commented:
It is not a PM message.  It happens before the PM is started, when all the network drivers are loading.  The last two things that happen are: the TCPIP driver is loaded, then the Ring O 2.2
video stuff.  Then a short pause and "socket: Network is down".

I've fixed the "hit any key to continue..." message by including
PAUSEONERROR=NO in the config.sys.
0
 
sfahey103197Author Commented:
In MPTS the only things I have installed are tcp/ip and Netware support.  No NetBIOS over TCP/IP.

>Take a look in the TCP/IP configuration - check which services >you are starting. Also check which network cards are activated,  >it may be that you have enabled a network card number which >does not exist in MPTS.

I checked the startup.cmd in the mptn/bin directory and it looks good.  The ifconfig statement uses lan0 which is the adapter specified in MPTS.  I hate to start the configuration notebook because it tries to change sendmail configuration (among other things).  What else can be going wrong.  setup.cmd is the only thing that's "called" from the config.sys (via mptstart.cmd).  
0
 
sbuftonCommented:
Try moving the call to the MPTSTART.CMD further down
your config.sys - perhaps some drivers have not been
loaded when it is being called.

In my config.sys, the MPTSTART.CMD is called after
all other entries referring to c:\mptn, and is
followed by all entries referring to c:\ibmlan, then
entries referring to c:\tcpip. Is yours in that
order?

0
 
sfahey103197Author Commented:
The new TCP/IP stack (4.02m) fixed the problem.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.