Enabling IPv6 in Windows 7

[Saab Dastard]

It might be worth going back to basics and trying to ping 169.254.1.65.

Hopefully both PCs will be using an APIPA address from the same range.

I presume that this is because they are connected NIC to NIC and are both set to request a DHCP address (and failing, hence APIPA).

SD

[Pelikal]

Ok, it didn't accept that number at first and checked the Mac. Number changed. Tried the new number. Enter Network Password to connect to 169.254.146.98\rob

Enter name/password and get specified network password is not correct.

Maybe the network password is something different....sorry it took a while to come back.

[Milo Minderbinder]

Pelikal

Saab's just pointed something out something that demands a further question......are these two machines being connected machine to machine, or via a router......?

trying to connect two machines and leaving the IP addresses to sort themselves out rarely works - you usually need to fix the IP addresses.

connecting both to a router is a far better idea
However if they ARE connected to a router, then the Mac isn't being allocated an IP address by it. Restart the router, then restart all the computers

I've should have realised that earlier - the 169. address is a giveaway, but didn't think about it 'till Saab commented

However, the last comment in your last post rather suggests that the user names and passwords don't match on the two machines. Nothing to do with separate "network" passwords - that went out with Win9X.

[Pelikal]

Never pinged before though I have ponged. Anyhow, I pinged the number above and it came back with:

packets sent =4, packets received =4 Lost=0.

I don't know what this means but guessing it sent and received ok.

[Pelikal]

Milo and Saab, both machines connected direct, no router. The user name and password are definitely the same. The computer names are different. I said right at the start this is my first attempt at networking but maybe I'm getting a grasp. Thanks.

[Pelikal]

Milo,

trying to connect two machines and leaving the IP addresses to sort themselves out rarely works - you usually need to fix the IP addresses

Ok, I don't know how to do this. I'll have a poke about and see what I come up with.

Perhaps I'm just being a fool thinking I can connect an 'old' G5 to a machine running Win7.

[Saab Dastard]

Perhaps I'm just being a fool thinking I can connect an 'old' G5 to a machine running Win7

Not at all, your problem is simply a lack of familiarity with the technology, not foolishness.

It doesn't matter how old the device is, if it talks TCP/IP it can talk to anything else using TCP/IP*.

At least at a connection level.

The problems tend to occur higher up the stack, when you try to to get a new application to talk to older kit that may not support that app.

However, SMB / CIFS (which is what we are talking about here) is an established standard, adequately supported by both devices.

You will get there, if you persevere. It's perfectly possible. I can't help with specifics because I haven't worked on a Mac for almost 20 years!

SD

* for the experts, I know I'm ignoring IPv6 here...

[mixture]

Ok, I don't know how to do this. I'll have a poke about and see what I come up with.

On one you setup an IP, say 192.168.113.1 with subnet mask 255.255.255.252, on the other 192.168.113.2 with subnet mask 255.255.255.252.

There you go, two directly connected computers on the same subnet being told what addresses to use rather than allowing them to unsuccessfully decide between themselves.

[Pelikal]

Thanks both for responses. I'll try a bit harder!

[jimjim1]

You can check what shares your PC is publishing from the command prompt with:-

###
Use your own computername.

C: \Users\jim>set | find /i "computer"
COMPUTERNAME=JIM1

C: \Users\jim>
###

C: \Users\jim>net view \\jim1 /ALL
Shared resources at \\jim1



Share name Type Used as Comment

-------------------------------------------------------------------------------
ADMIN$ Disk Remote Admin
C$ Disk Default share
IPC$ IPC Remote IPC
test Disk
Users Disk
The command completed successfully.



The "$" shares are so called hidden shares that do not respond to a remote net view but which can still be used if you know the name.


PS
Your first cable was fine since for ANY sharing to work you need two way communications on the cable.

Oh yes, try with a blank workgroup.