Networking Noob!

[dtravis7]

I have never tried firewire for networking. Always Cat-5 cable plugged into the network ports. I have no idea if that works or not on W7 and can't test it as my W7 Netbook has no firewire.

[FastMac]

To be honest I never thought Windows (whatever version) has ever been able to use firewire as a networking method, in fact PC's have never even called it firewire as it was only on maybe one in 50 PC's and called a 1311 port or similar and on cameras it is called iLink. So maybe no surprise that kernel panic resulted from firewire between the two machines because the PC thought that a music device or digi-camcorder was connected.

[dtravis7]

Originally Posted by FastMac

To be honest I never thought Windows (whatever version) has ever been able to use firewire as a networking method, in fact PC's have never even called it firewire as it was only on maybe one in 50 PC's and called a 1311 port or similar and on cameras it is called iLink. So maybe no surprise that kernel panic resulted from firewire between the two machines because the PC thought that a music device or digi-camcorder was connected.

Agreed completely!!

I have never even seen anyone using Windows try to network using Firewire. Usually FW is called 1394 on pretty much every Windows PC I have ever seen. Sony called it iLink on some of their Firewire devices.

I thought he was talking a normal network hooked up to a Switch or Router all this time!

[Scooter]

Yep that's what I've been trying to do, connect via FireWire. So I need to direct connect via Ethernet cable instead. My router is full. All 4 ports used by my DSL Modem and 3 computers on my LAN. None of us can see each other but we do get the DSL I/O use. I wanted to slave the PC to HAL.

SOOOoooooo. Next question. IF I add another Ethernet card to HAL and then link the two might that work?

Speaking of the Kernal Panic. HAL told me this morning "I'm Completely Operational And All My Curcuits Are Functioning Perfectly". So apparently the panic yesterday has not affected him permanently.

THANX Guys. This is truely a class in Networking 101. I'm learning quite a bit from all y'all.

[FastMac]

Yes I think (afaik) that ethernet to ethernet direct between machines should allow communication, you may need to set up a new connection in windows but the Mac should just get on with it.

dtravis7, what was that software can't remember if it was PC or Mac, could be called "dave" used to make PC all Mac friendly or vice versa???

[Scooter]

I remember that one. Dave is/was a Mac App for getting Mac/PC talking.

"Hi I'm a Mac"
"And I'm a PC"
"How you doin PC?"
"Well not to good Mac. Sales are down, The European Union is sueing me, and everyones afraid of Win7."
"Aww that's to bad PC. I set record profits and even have a new Tablet coming out in January. Pixar is in control of Disney animation studio and there's this fella named Scooter who has a G4 named HAL that's blowing my mind"
"Oh great Mac, another HAL. Just what I needed. It'll shut the pod bay doors on me."

[Scooter]

OK, I got my hands on another Ethernet PCI card. Have empty slot left and as soon as I get back to Bat Country, I'm gonna plug in the card and try the link-up as instructed. Setting up the IP and Network stuff. I may not get to this for several weeks thou. I'm not near HAL and wont be for a while. Do Y'all think I'll need a "reversing" eNet cable? Or should a straight thru cable suffice?

[dtravis7]

Originally Posted by FastMac

dtravis7, what was that software can't remember if it was PC or Mac, could be called "dave" used to make PC all Mac friendly or vice versa???

I know exactly what you are talking about but also forget the exact info. I guess I missed this post last time I was here. I know there was something for Mac OS called Dave or maybe on the Windows end.

Found it, it was Dave and worked with older Mac OS but now there is an OSX version also!

http://www.thursby.com/products/dave.html

The site only talks about the OSX version now but I found another URL that mentioned Mac OS 8.6 and 9.

http://www.atpm.com/network/files/mac_pc.htm

[dtravis7]

Originally Posted by Scooter

OK, I got my hands on another Ethernet PCI card. Have empty slot left and as soon as I get back to Bat Country, I'm gonna plug in the card and try the link-up as instructed. Setting up the IP and Network stuff. I may not get to this for several weeks thou. I'm not near HAL and wont be for a while. Do Y'all think I'll need a "reversing" eNet cable? Or should a straight thru cable suffice?

Do keep us posted when you get back to HAL!

All the Macs I have here work without a CrossOver cable with each other anyway. I have not used a crossover cable in ages now as I have so many switches and routers around the house.

[Scooter]

OS X to W7 networking ....... FAIL!!!!!!!!!!

After beasting my brains out and guessing at most all of this stuff. W7 finally tells me that it can't network on EEEE1394 or iLink.
I have DAVE installed on HAL
I was able to get all of the LAN IP's for all of the computers and the D-Link router but not find the 3Com addy shown anywhere. Not sure if it neds one or what.

All Ethernet connected for the following.

DSL Modem in my Net IP address. > Router *J* a D-Link 5 port has a LAN IP of xxx.xxx.0.1
Router *J* feeds the (10.4.11) iMac at xxx.xxx.0.101
and the XP-eMachine at xxx.xxx.0.103
and my 4 port 3Com router > which in turn feeds the W7-HP at xxx.xxx.0.100
And (10.4.11) HAL at xxx.xxx.0.102

So here's what happened.
•HAL can see the iMac and swap files in and out with no problem, via the netwokk window.
•HAL can't see the W7-PC at all.
•The iMac cannot see HAL or his files.
•The iMac can mount the W7-PC on it's desktop. Unable to do much but can see it.
•The W7 PC can't see anytning at all. Won't connect to the homegroup.
And I haven't even tried to mess with the eMachine and it's settings. So no telling what will happen there.

I think I'll just use a USB HDD to swap files around. Seems a whole lot easier to just plug it in to HAL and then the PC.