TCP/IP Ethernet not responding (and DAVE)

I'm trying to hook up my MAc to my NT box via Services for Macintosh and DAVE. Neither are working and I think it's for the same reason. I have setup my TCP/IP settings as Ethernet/Manually/IP=192.168.0.2/subnet=255.255.255.0 but when I try to use either Dave or start appletalk (using NT as the Router) I get errors. From Appletalk I get "An error occurred attempting to use ethernet. make sure your network conntections are correct" and from DAVE I get a "The NetBIOS Driver is not working". I'm a pretty competent computer guy and I'm sure I've set everything up properly. In fact I should mention I had the whole think working once but came back a few hours later and the NT server had rebooted and nothing's worked since. NT looks like it's starting all the services up properly (no errors in event log).

when reinstalling DAVE it found that TCP/IP is not working when finishing the setup.

How can I tell where the problem lies? With the Mac? With OT with the card? With NT? Will I get these same errors if everything on the mac is ok?

As far as I can tell the cards are fine (I get the same errors with two different Ethernet cards on NT) and the connections fine. The loopback test on my Mac adapter passes when trying to connect to NT but freezes when trying to connect to Win95 (Dual boot machine).

Setup:
Mac OS 8.1
OT 1.3

PC:
NT 4 service pack 5

Bugger me, please help!

Dave
deal051298Asked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
joelanConnect With a Mentor Commented:
Before you do any other trouble shooting, verify your cable is working.  Either take it to a local network shop or try to install it between two systems that you know are working.  Once you have a cable that you are sure is good, then I would set the the speed of the NICs to 10bt and try to get it working from there.
0
 
deal051298Author Commented:
Update:
Using OTTool to diagnose problems on the mac I get "Open Transport is returning an error (-3205). Has TCP/IP been configured?". I know the TCP/IP settings are correct.
0
 
weedCommented:
Is your appletalk/network port set to ethernet? Have you reinstalled OT?
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
deal051298Author Commented:
I have re-installed OT a couple of times (this still happens with a fresh system install). Appletalk won't let me choose ethernet - I get the "An error occurred attempting to use ethernet..." message and then it goes back to printer port.
0
 
weedCommented:
ahhh BINGO...youre missing some vital appletalk/ethernet parts...Is there an ethernet cable actually plugged into your ethernet port? Do you get the same problem when booting off a fresh system?
0
 
deal051298Author Commented:
Yeah, there is an ethernet cable plugged in and I get the same problem after doing a clean install of a complete new system with appletalk and OT. Do you think I would get these errors becuase of a cable problem?
0
 
deal051298Author Commented:
Thing is, how do I know if the problem is at the Mac end or the PC end? I get the same problem with 2 different ethernet cards on the PC but it might be a software problem on that end as well.
0
 
weedCommented:
It could be a bad cable but as long as a good cable is plugged into the port you shouldnt get the "appletalk error" message.  Is it a crossover ethernet cable or do you have a hub?
0
 
deal051298Author Commented:
Crossover cable.
0
 
weedCommented:
hmm yes then definitely if you have a bad cable or the PC is mucking up you will have problems with the appletalk error.
0
 
benstockCommented:
When did you apply SP5?
Are you running other services on this box (eg RAS or Exchange Server)?
0
 
ajoconnorCommented:
Is there any response from using a ping command to either machine. Even if you are not logged in to the NT server or domain you should still be able to use ping.
If there is no response it will suggest that it could be an NIC/TCP-IP setup or cable problem.

?
On the other hand have you profiled the MAC name in the Server Manager list.
?
0
 
ajoconnorCommented:
Is there any response from using a ping command to either machine. Even if you are not logged in to the NT server or domain you should still be able to use ping.
If there is no response it will suggest that it could be an NIC/TCP-IP setup or cable problem.

?
On the other hand have you profiled the MAC name in the Server Manager list.
?
0
 
deal051298Author Commented:
I can't ping either machine from either box. This'll make it a driver or cable problem? I'm 99% sure the NIC's are alright.
0
 
deal051298Author Commented:
The network was running earlier and I didn't add any additional services or apply the SP5 after this so the NT box shouldn't be interfering.
0
 
mazurCommented:
Sounds like the problem is on the NT end. If you have another Mac, you could try hooking them together to verify....
0
 
ajoconnorCommented:
What happens when you ping 127.0.0.0 or ping localhost on the Mac & NT Box ?
What response do you get ?
0
 
williams2Commented:
To "ajoconnor": I suppose you mean 127.0.0.1, as 127.0.0.0 is NOT a valid IP adress. :-)

To "deal":
I can only support you with some advises regarding your NT Box.
It is of VITAL importance, that you reinstall SP5 after installing your network, as the servicepacks will ONLY upgrade the components installed in you setup. I have solved different weird networkproblems by repatching the SP5, so I suggest you go repatching immediatly before proceeding..

There's even though different aspects to this:
Do you have a sufficiently installed network? (If your browser is setup to run upon the existing LAN and is altering the RAS manager automatically, then you don't!)
Do you have a working RAS / Internet connection ?
If Yes: Is it stabile at this very moment ? if not, then go remove it/restart the NT box/reinstall the TCP protocol - trust me, that is important!
If no: Have you tried to point the gateway at your own machine ? (You can test this by trying to setup a cheap ftp server - like the freeware WarFTP - if this works, your TCP/IP should be working allright)

Now to the NIC's:
1. When pinging the 127.0.0.1 (localhost) this will confirm that your TCP/IP network is functioning at some point, but it WON'T be a confirmed test of your network adapters.
2. If you in your NT desktop have a systray applet for your NIC like the 3Com NIC's do, this should be enough testing the NIC, else you can test your configuration by doing the following:
If you are using PnP adapters on the NT box, please try using "Jumper settings", else go test your HW settings in the "Windows NT Diagnostics" program found at:
"Start"->"Programs"->"Administrative Tools (Common)"->"Windows NT Diagnostics"
Now go to the "Resources" page and lookup both the IRQ/PORT settings matching your NIC's - They must match you NIC settings.

I hope this could bring you a step further to a solution.

Regards,
Williams
0
 
crojasCommented:
Just a guess, What kind of NIC's you are using?
If the NIC's are 10/100 and you're using a crossover cable maybe your problem is the autosense in the NIC's, try using the utilities to fix the speed to 10 or 100, because sometimes the NIC's try to autosense between them in a loop.
0
 
deal051298Author Commented:
sorry joelan, a reinstallation of the SP5 after installing my network solved the problem. I could ping 127.0.0.1 and my card 192.168.0.1 but not the other machine.

Thanks everyone. Most responses I've ever got to a question!

Dave
0
 
deal051298Author Commented:
Oh ****. I was supposed to reject your answer. I'll be posting points for williams2 when I can afford it (in this subject area).

Damn!
0
 
williams2Commented:
Hmmmmm....

That's ok, the primary thing is, that you solved your problem ..I'm glad I could be at any help..

...see you around ;-)

Regards,
Williams
0
All Courses

From novice to tech pro — start learning today.