can't get tcp/ip on dos lan driver to work

T4x series specific matters only
Post Reply
Message
Author
dunk
Posts: 12
Joined: Wed Feb 09, 2005 8:26 am

can't get tcp/ip on dos lan driver to work

#1 Post by dunk » Wed Feb 09, 2005 8:51 am

i'm trying to get tcp/ip running under dos on a T21 (model 2648-ED2) in order to run ghost over a network. i've done this with other computers with different NICs and am attempting to adapt the configuration used there for the T21. i've downloaded the dos driver (eftpntel.exe) from the package here:

http://www-307.ibm.com/pc/support/site. ... IGR-4K4PWS

and modified my protocol.ini as described in the NTPUSH.TXT file of the package's PUSH directory. here's the resulting protocol.ini:

--------------------- PROTOCOL.INI ----------------------------------
[protman]
drivername=PROTMAN$

[pktdrv]
drivername=PKTDRV$
bindings=nic
intvec=0x60
chainvec=0x66

[nic]
; drivername = rtsnd$
drivername = E100B$
CACHEFLUSH = 1
; Medium type Medium = _Auto; (optional) Network Address ; NETADDRESS =
@000000000000; (optional) Node Address ; ETHERID = @000000000000; (optional)
Adpater's Bus Number ; BusNo = 0; (optional) Adpater's Device Number ;
DeviceNo = 0; (optional) Adpater's TX Early Threshold ; TxFiFo = 5
--------------------- END PROTOCOL.INI ----------------------------------

the E100B.DOS driver loads without errors as do the protocol manager and
packet drivers. here's my config.sys

---------------------- CONFIG.SYS --------------------------
DEVICE=a:\himem.sys
DEVICE=a:\net\protman.dos /I:\net
DEVICE=a:\net\dis_pkt.dos
DEVICE=a:\net\E100B.DOS
LASTDRIVE = Z

---------------------- END CONFIG.SYS --------------------------

the autoexec.bat is just one line:

\net\mybind.com

here's the output of the bootup:

IBM Protocol Manager Version 2.1
MAC/DIS to Packet Driver converter loaded. Version 1.10
Copyright 1991 FTP Software, Inc., All rights reserved.
Portions Copyright 2000 Symantec Corporation

Intel (R) PRO PCI Driver 4.22 083100
Copyright 1995 Intel Corporation. All Rights Reserved.

Defaulting to NIC found in slot 0x0003 <----- no idea if this is right. how to check?
PCI ID: 8086 /1229/8086/2408/0009

MS-DOS LAN Manager v21. Netbind
IBM Netbind version 2.1


when i run ghost, the "peer-to-peer" functionality is enabled indicating that it thinks i should be able to do the network transfers. however, when i set it in slave mode and try to connect from another machine as master, it fails on the master. when i try to ping it from the other machine, the pings fail (pings succeed on the other machines on which i've done this). the green link light on the T21 is on and the orange activity light flashes when i run the ping. the networking works fine under windows 98. my BIOS is 1.06b (KZET5WW) Date: 2001-04-17. any idea what the problem is?

also, when i use netbeui under ntclient to map a drive letter in dos, it works fine. when i go into ghost, ghost sees the mapped drive and i can specify an image file name to write to on this drive. however, ghost then fails with a usage error 662 "cannot create image file". when i exit to dos, and try to look at the drive i get an extended error 53.

thanks for any help

topper24hours
Posts: 1
Joined: Wed Dec 28, 2005 11:52 am

Her is the answer!

#2 Post by topper24hours » Wed Dec 28, 2005 11:54 am

The 662 error means you have one usb 2.0 device and one usb 1.1 device; a big no-no. The culprit is probably a usb mouse. Your external drive should be the ONLY usb device. Also remove from docking station and power the machine directly.

Post Reply
  • Similar Topics
    Replies
    Views
    Last post

Return to “ThinkPad T4x Series”

Who is online

Users browsing this forum: No registered users and 3 guests