Text 32, 61 rader
Skriven 2004-06-15 22:42:00 av Will Honea (1:106/2000.0)
     Kommentar till text 31 av Mike Powell (1:2320/105.0)
Ärende: Networking Problems
===========================
Mike Powell wrote to Will Honea on 06/14

MP> | Nothing is going to help until you get the cable errors fixed - it's
MP> | not see a connected interface and is quitting right there.  With the
MP> | 3c509 I had to make a couple of DOS passes with the config program to
MP> | get mine all set up. and that message was what I got until I did.  Oh,
MP> | one tip on the 3c509 in particular:  If the setup has a modem speed in
MP> | the setup screen, make sure it is set to 9600.  Some of the dirver
MP> | versions got all upset if it wasn't, even if the card didn't HAVE a
MP> | modem on it.
MP> +-[WH=>MP]
MP>  
MP> I changed the baud rate to 9600, and now I get a new error, while
MP> using the "logon" command you suggested.  I did not receive this
MP> error when I tried it before changing it to 9600 (I only got the
MP> familiar cable error).
MP>  
MP> A box pops up that says "System Error - Detached Process ID 49." 
MP> The box contains a SYS3175, and says that the program cannot go on. 
MP> Checking the registers displays an Access Violation with NETAPI.DLL.
MP>  I tell it to end the request. However, the REQUESTOR appears to
MP> continue to run, eventually ending with a new error message, "Net
MP> 3062: The Sub-Service PEER failed to start."
MP>  
MP> At least the errors are different now.  ;-)

Ah, progress.  I never did completely figure out WTF the problem was
with the non-existant "modem" and the 3c509 but that 9600 baud
suggestion came across years back when it was a current card anf I've
always used it just "because".

OK, now you lose the obvious message.  Check \ibmcom\lantran.log and
see if it has any more info.  Any time I start mucking with different
NICs I first concentrate in getting them to run strictly tcpip - to see
if I can ping myself and/or other machines.  One of the challenges I
get every time I put a 3c509 into a box that does multiboot with a
Winxx version.  Invariably, Winxx will hose the settings for the card. 
Until recently, the house was networked with RG58 and used 10base2
links.  Win would always insist that it was going to use 10base10 and
the RJ45 connector come hell or high water so I got pretty good at fast
resets of the 3c509 nvram from a DOS boot.  Simplify life and disregard
PEER and NETBEUI until you get the physical link running with tcpip -
much better diagnostics and much less to go wrong with settings.

Just a a prelude to what may come after getting tcpip running, it
seems that everytime I do any kind of messing with protocols that
involve changing or removing/adding NETBEUI after initially installing
it I get an "invalid NETWKSTA.200" error.  Never have figured out just
why, but I do.  The recover is to re-install networking over what I
have and specify NETBEUI as a protocol during the install.  

See what happens with straight tcpip and ping.  From there it's
downhill to the finish.

Will Honea <whonea@codenet.net>

___
 þ KWQ/2 1.2i þ I DID Read The Docs!  Honest!  Oh, *That* page...

--- Maximus/2 3.01
 * Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000)