On Thursday, April 3, 2003, at 12:29 PM, Chris Olson wrote: > On Thursday, April 3, 2003, at 11:51 AM, b wrote: >> >> Well, that is exactly the way my setup, in VPC 6 is,and the bytes go >> out, but the 'returns' don't come in. All internet activity comes to >> a halt, waiting for pages that never arrive I just tried it, and the Shared Networking works fine. I set Win 2K to get an address via DHCP. It got an address of 192.168.131.71 with a default gateway of 192.168.131.254. I switched my PowerBook from static to DHCP on our network (which is basically the same as pppoe in that you get a dynamic address). On our network, my Ti still has a private address of 192.168.1.231, which is masqueraded thru two more routers before it hits the outside world with a public IP. So if it works under my situation, there should be no problem with your setup. I think it's a Windows XP problem. Remember that XP is pretty brain dead when it comes to networking. If it encounters something a little out of the ordinary it borks the whole setup. That's the price you pay for an operating system that tries to do everything for you and doesn't give you access to the nuts and bolts of what makes it work. In Win XP, type cmd at the run prompt to get a shell - you can run netstat /a and ipconfig to see what you're getting for a network setup under DHCP. Windows XP likes to "phone home" when you fire it up too - if it can't contact Microsoft's database when it thinks it's on a network where it can, it'll have other problems too, especially like search features taking forever to complete. The other thing to consider is how are your firewalls configured in OS X and Windows XP? Have you looked at those settings? -- Chris