• Please review our updated Terms and Rules here

Can't seem to get mTCP working...

RWallmow

RWallmow

Veteran Member
Joined
Oct 19, 2006
Messages
1,791
Location
Anoka, MN USA
I am not sure if its my packet driver or something else. I tend to think its NOT the packet driver, but I am VERY new to mTCP, I have always used MS-NET for DOS networking (which has its own drivers), but its not really suited to an 8086 machine (if it will even run, IIRC it needs 286, I didn't try).

Packet driver seems to load like it should:
Code: 
C:\MTCP>SMC_WD 0x60
...
System: 8088/8086 processor, ISA bus
Packet driver software interrupt is 0x60 (96)
Interrupt number is 0x3 (3)
I/O port 0x280 (640)
Memory address 0xD000 (53248)
NIC 8390
My Ethernet address is 00:00:C0:EE:5C:2B

I am using a real basic CFG file:
Code: 
packetint 0x60
hostname DOSRules
IPADDR 192.168.1.95
NETMASK 255.255.255.0
GATEWAY 192.168.1.1
NAMESERVER 192.168.1.33

Whenever I try to ping, telnet, ftp, htget, none of them can resolve DNS, nor can they make any connection via IP, but I do see flash of activity LEDs on the hub I am connected to, but all of them come back having sent something like 18-20 packets, but receiving none.

I have also tried using DHCP and it times out with:
Code: 
Error: Your DHCP server never responded and no packets were seen on the wire.
Check your cabling and packet driver settings.

I do see a flash of activity LEDs on every attempt of DHCP as well, but always times out.

I should note that I started out cabled into a gigabit switchport, however I have seen some 10Base NICs that would not work on 100/1000 switches, so tried everything again on a 10Base-T hub with the same results. The NIC in this PC is tested working, I tested it in a 286 running MS-NET client and I can ping and map drives just fine. The PC I am trying to get this all working on is my IBM PS/2 Model 25 with a NEC-V30, 640k RAM, 400MB HD on TMC-841 SCSI card, and the NIC is a SMC WD8003 card.

Any ideas would be appreciated:confused:
 
Try this instead;
NAMESERVER 192.168.1.1

I'm guessing that you're not actually running a DNS server on your LAN...
 
Krille said:
Try this instead;
NAMESERVER 192.168.1.1

I'm guessing that you're not actually running a DNS server on your LAN...
Click to expand...

I am actually running a DNS server, 192.168.1.33 is my Domain controller/DNS server, but I had also tried 192.168.1.1 which is my router's DNS server. Doesn't help.

DNS doesn't seem to be the issue, its not receiving ANY packets from what I can tell, but it SEEMS to send them.
 
You are in Anoka. We are nearly neighbors.

Do you have the packet driver parameters correct? What you are describing sounds like the packets are being sent, but the incoming packets are not being received. DHCP will give you a warning that tells you when it doesn't receive any packets, which is an indication that the IRQ that you used on the packet driver is not correct.


Mike
 
RWallmow said:
The PC I am trying to get this all working on is my IBM PS/2 Model 25 with a NEC-V30, 640k RAM, 400MB HD on TMC-841 SCSI card, and the NIC is a SMC WD8003 card.
Click to expand...

While it is unlikely, do you have a second serial port (IRQ 3) or does your SCSI card have a ROM or memory window at D000? I ask because those are the resources the NIC is trying to use, and I want to rule out conflicts. Almost every time I've had trouble with mTCP, it has been the NIC not behaving like it was supposed to, so that's why I ask.

My litmus test of whether or not everything is working is DHCP. If I get an IP address, everything is golden. Continue to use that as your test.
 
Trixter said:
While it is unlikely, do you have a second serial port (IRQ 3) or does your SCSI card have a ROM or memory window at D000? I ask because those are the resources the NIC is trying to use, and I want to rule out conflicts. Almost every time I've had trouble with mTCP, it has been the NIC not behaving like it was supposed to, so that's why I ask.

My litmus test of whether or not everything is working is DHCP. If I get an IP address, everything is golden. Continue to use that as your test.
Click to expand...

SCSI card is jumpered to be at CA00 and IRQ 5, and I only have the one onboard Serial port.

I just found a copy of the config utility for this NIC, and its set to IRQ 3, I/O 280, and Memory 0xD000 just like the packet driver has been detecting it as. I don't know if anything else is at D000 on a model 25 that might be conflicting, but I don't think so.

I think I might have to throw in the towel on this NIC and try to find my AUI transceiver (or hang some coax off my hub) and use one of my Etherlink II cards. I have some Etherlink III cards too, but I the ones I have are not the right revision to do 8-bit (I have tried on a 286 box).
 
I had basically the same problem with my tweener. I striped everything I could out, turned off as much as I could in the bios and started just with the basics and a network card. My problem ended up finding the correct packet driver for the card and setting the interrupt. I do have most of the mTCP programs working but I had to set a static ipaddress, never could get it to acquire a dynamic address from my DHCP server. I am sure it is something I have configured wrong.

Good luck with it and thanks to Mike for a fantastic group of software.


Jimmy
 
Trixter said:
Try IRQ2, nothing should be using it in your model 25.
Click to expand...

Believe it or not I got it working!!! I found a switch for the config program to turn off PNP on the card, and then I ran config again and forced it to IRQ2 and D000 and it's finally working!!!
Pulled a DHCP address right away and pings like it should!!

Here is a link to the Driver package which includes EZSETUP.EXE which lets you configure the WD8003 cards.

EDIT: I should note I tried IRQ2 once before, but this was before I found the command line switch for disabling PNP, it appears that PNP was what was holding this back somehow.
 
mbbrutman said:
You are in Anoka. We are nearly neighbors.

Do you have the packet driver parameters correct? What you are describing sounds like the packets are being sent, but the incoming packets are not being received. DHCP will give you a warning that tells you when it doesn't receive any packets, which is an indication that the IRQ that you used on the packet driver is not correct.


Mike
Click to expand...

Thanks Mike for the help on this offline!!!

And thanks Trixter for making me try messing with IRQ's again, and making me go back to look at the cards documentation the one last time I needed to find the -nopnp switch for EZSETUP.
 
You must log in or register to reply here.
Back
Top