I have had my small LAN setup using IPX/SPX for years. I need to set up one system to Wake on Lan. I am under the impression that I have to switch to TCP/IP to do that. Is that right? Anyway, I have set up the systems as shown below. Each system shows it's own drives in Network Neighborhood but not the other system. I cannot ping the other system either way. Any suggestions on what I am missing would be greatly appreciated. Client for Microsoft Networks Dial-up adapter Realtek RTL8139 PCI Fast Ethernet NIC TCP/IP -> Dial-Up Adapter TCP/IP -> RTL8139 PCI Fast Ethernet NIC File and printer sharing for Microsoft Networks The Identification panel has the same Workgroup and different computer names.

Darn, I forgot to mention that I have the Network addresses set up as 192.168.10.1 and 2 and the subnet as 255.255.255.0

Maybe I should also mention that I tried 192.168.0.1 and 2 also.

"Wake on LAN" sends a "magic packet" to each machine on the network and if that machine has the right ID number and is WAL enabled it will boot up. You can use either TCP/IP or IPX/SPX to send the magic packet but you have to 'bind' the protocol to Netbios or it won't know which one to use. I'd go ahead and put IPX/SPX back on the system and bind to it: It's used on too many devices and older programs to get away from, really. The other thing you have to do is go into My Computer and for each drive, folder, or program you want to share enable sharing. The other PCs on the network won't even "see" it otherwise. You didn't say what your OS was but for Win9x set up a password to connect to this, for WinNt/2K/XP add the user account for each person on the network and add these to the permissions for that resource. Log on under that account on any machine on the network and you can access the resource. Note: I don't think the "Administrator" account can be shared, sorry. You'll have to create another one.

Thanks very much OrionCA! That's great news. I will stick with IPX/SPX then. I've always used NetBios with IPX/SPX so that's not a problem. I'm the only user so passwords is not a problem either. Now I just have to get the Wake on Lan working. That should be fun. Thanks VERY much!

I've tried to get the Wake On Lan working with Magic Packet and it doesn't work. It seems to be looking for a TPC/IP address in the `IP Broadcast Address' window, which I don't have because I'm using IPX/SPX. I get a Windows socket error: (11001), on API `ASync lookup'. I also tried a couple of other programs for WOL and remote shutdown/boot which failed. They all seem to be oriented towards TCP/IP but they do not say it's required. I am really lost.

I work with WOL on a daily basis and in the rather large WAN I work on, the packets are sent to a MAC address, not an IP address. I'm not familar with "magic packet" (is that an application, or just what you call the packet sent to the WOL?) but if your network is setup properly, it should work regardless of which protocol stack you are using.