Author Topic: Internet sharing with a PC & a Mac (Read 6145 times)

Nom_Anor · « **on:** 2004-03-31 14:45:58 »

I am currently trying to connect my oldschool G3 (running os10.2), to my laptop (Ms XP), using a crossover cable. I have a wifi card connecting the internet to my lappy, and for the love of god I can't get the mac to connect to it. I can't even ping the sob.

Here is what I have done:

1. Did a google search all up and down that area

2. Tried their way of setting it up... using a Client for MS networks, and File/Printer sharing enabled on the NiC, as well as sharing the wireless connection.

3. Then, I manually set the IP of my lappy to 192.168.0.1, and the Mac to 192.168.0.2, no DNS, or WinS, as per the directions. Subnet set to 255.255.255.0. The ip on the evil mac is 192.168.0.2, manually assigned, same subnet, Gateway set to 192.168.0.1 (lappy's ip)

4. I cannot ping the mac, and the mac cannot connect to pc at all. I tried different IP's for my lappy, and changing the mac around, since I wasn't sure if one of the other comptuers I have was using the wi-fi @ 192.168.0.2, but nothing was there when I pinged it. Go fish.

Does anyone have any clues on this matter?? I've dumped wayyy too much time into this box... I just don't have the $100 to waste on an airport card for that computer.

Oh... one more note. The NiC on my lappy shows a good connection to the mac, and data going back and forth. I snagged a tester from my work, both net cards are good, and the cable is good 10 ft crossover. **running out of ideas**

DeadLajik · « **Reply #1 on:** 2004-03-31 15:56:10 »

Are you 100% sure that the cable is a cross over cable and not some regular 568A or 568B ethernet cable?

What are the colors on each jack?

For a crossover the following is usually used..

Jack 1
Pin 1: White-Orange
Pin 2: Orange
Pin 3: White-Green
Pin 6: Green

Jack 2
Pin 1: White-Green
Pin 2: Green
Pin 3: White-Orange
Pin 6: Orange

The other colors are not used in 10/100 ethernet.

I say "usually" above because you could also mix up the colors anyway you want as long as the Receive-Positive pin wire is the same wire as Transmit-Positive and the Receive-Negative pin wire is the same wire as the Transmit-Negative.

Nom_Anor · « **Reply #2 on:** 2004-03-31 16:22:31 »

I am 100% sure. As in, it was crossover when I bought it. I used a 'Fluke Net tool' to check the cable. It showed the pairs were perfect. See the above post

Nom_Anor · « **Reply #3 on:** 2004-04-01 22:19:04 »

Halloo....anyone have any ideas on this??

Aaron · « **Reply #4 on:** 2004-04-01 22:38:59 »

I've done this before... looks like it should be working.

The setup process looks good. You have a non-firewalled network connection on the laptop (Windows XP), set your wireless to share the internet to the wired connection (connection properties -> Advanced tab - - allow other users to disable/control this connection should be UNchecked). Then your wired connection will have an assigned address of 192.168.0.1 and subnet mask of 255.255.255.0. The Mac's IP should be 192.168.0.x, subnet mask 255.255.255.0, router 192.168.0.1, and you should copy the DNS servers from the laptop's wireless connection (doesn't look like you did that, but that shouldn't affect connecting to the PC, just resolving internet DNS addresses - you won't be able to get online via a web browser unless you type the IP address of a site, not it's DNS name).

Pinging doesn't always return anything if the device you are pinging doesn't allow/support ICMP Echo Requests. If you're using MacOS X and the firewall is on, this might be the case. You SHOULD however, be able to ping the laptop from the Mac using the Terminal app - you can't share an internet connection to a firewalled connection in Windows XP RTM/SP1 (you can in SP2), so it should always return pings.

The Mac shouldn't be conflicting IPs with anything, anyway, since it's 192.168.0.x only exists on the mini-network between your Mac and laptop.

My best guess? Do you have the firewall on in MacOS? This would keep you from pinging it, and if you didn't copy the DNS information, that would keep the Mac from getting online.

Also, make sure you enabled Internet Connection Sharing, but didn't turn on a Network Bridge. You can accomplish the same thing with a bridge, and might be a little easier, because then you don't have to manually set IPs or anything. Maybe you should try that...

Nom_Anor · « **Reply #5 on:** 2004-04-01 22:56:21 »

Thanks Aaron. I'll give that a shot when I get home tonight. I didn't add the dns servers...but I know that the mac doens't have any firewalls up. I'll check the rest of the settings.

Aaron · « **Reply #6 on:** 2004-04-01 23:02:15 »

Remember, OS X (at least newer versions of it) has a built-in firewall, but I dunno if it ever "sneaks" on like I've seen the Windows one do.

Using a bridge is another option. It's pretty easy... to set it up:

- Neither of your connections on the laptop should be firewalled, neither should have a set IP address (set both to auto), and neither should be shared. (If any of that is the case, you will get an error while creating the bridge, and then need to delete it and try again.)
- Select them both in the Network Connection box, right-click and "Bridge Connections."
- Your Mac should be set to automatically grab addresses via DHCP.

This is all assuming you have DHCP on your wireless. If you manually set addresses, then just set the bridge on the laptop to like you had it before, and set the Mac as if you were adding it to the network as a wireless computer.

This way, your laptop will just foward stuff from your Mac out to the wireless network. Your Mac will grab address info off of the wireless DHCP and should have its own external address on the wireless network. (With regular Internet Connection Sharing, the Mac has an address "behind" the laptop's, and there's no way to get directly to it unless you set up some kind of port forwarding.)

The biggest disadvantage to this for me is I like to keep my connections firewalled, and you can't firewall the bridge. Fortunately, it appears that SP2 fixes this, at least in the RC1 build it is possible to firewall whatever you want.

Nom_Anor · « **Reply #7 on:** 2004-04-02 00:38:55 »

Well Aaron...God must hate me today. It doesn't want to work... no matter what I do. both net cards work just fine... that mac is too much of a piece of sheet to work is all I can guess. Blasted g3. Oh well... thanks for the info though.

DeadLajik · « **Reply #8 on:** 2004-04-02 00:58:05 »

Don't give up Nom,

I still think it's a hardware problem, even though I don't have experience with either OSX or XP (but I don't think XP is that different in networking then 2000).

Can you connect the G3 up to the internet directly ?

Nom_Anor · « **Reply #9 on:** 2004-04-02 01:44:44 »

Yeah. If I take my G3 upstairs, and plug it str8 into the router, it goes without a problem... obviously, then I am setting everything to connect via DHCP, fully auto instead of a manual connect.

Maybe I mod the case into a beck's mini-keg cooler. :wicked: Then I would actually get some use out of it.

**edit... PPC Debian hated this computer. Aparently Mac's aren't like PC's in the fact that they simply can't just run Linux, they need a separate boot loader, different than the one that comes with Debian. And, if your mac is a certain age, you have to go into the open firmware, and change the settings MANUALLY. And who the hell writes firmware in REVERSE POLISH notation. Stupid steve jobs. I hate that man. He's more of a douche than Bill Gates. And to get to that level of doucheness, it takes work. :z

Aaron · « **Reply #10 on:** 2004-04-02 02:45:40 »

Hmm... Once, I installed "Yellow Dog Linux" on a G3 iMac (but a little slow with only 64 MB of RAM). This was quite a while ago, I dunno if that distro is still being updated ^^
But it installed it's own boot loader ("Press L for Linux, 9 for MacOS 9, or X for MacOS X") and worked fine on my high school campus network.

Heh, I guess you can try Linux on it if you have nothing else to do

Nom_Anor · « **Reply #11 on:** 2004-04-02 14:05:48 »

Yeah... you see, the school was probably using bootx or yaboot to configure the bootloader. Bootx WAS supposed to work for me. But it didn't.

*edit.... can't seem to spell today

Aaron · « **Reply #12 on:** 2004-04-02 16:25:55 »

My school didn't do it, I did it. (I did it at school, though.) And I really didn't have to do much... I set up two partitions, installed MacOS 9 on one of them, and booted off the Yellow Dog CD and installed it on the other. It did all of the boot loader stuff by itself

Ah well.