Forum Moderators: open
Computer 1 running Windows 2000 Pro with a NIC and a usb cable modem
connected via crossover cable to Computer 2
Files are set up to be shared on Both. Each can see the other in My Network Places.
Computer 2 XP and a NIC
The Xp Computer 2 can access computer 1 shared files and use the printer, but cannot access the internet.
Computer one cannot access anything from computer 2. "The network path was not found" Also get this
not found error typing a path into run.
Computer one can ping the internets adapter but cannot ping the XP computer. However the XP computer can ping the Win 2000 computer, but not the internet adaptor.
Settings
Computer 1 Win 2000:
Client for Microsoft Networks
File and printer sharing
NetBEUI Protocol (if I remove this, XP machine loses connection)
Internet Protocol (TCP/IP) properties - use 192.168.0.1 subnet 255.255.255.0 DNS left blank. Enable NetBios.
Computer 2 XP
Client for Microsoft Networks
Qo S Packet scheduler
File and printer sharing
Internet Protocol (TCP/IP) properties - use 92.168.0.2 subnet 255.255.255.0 (I've tried these on automatic as well) DNS left blank. Enabled NetBios.
I've read and tried all kinds of conflicting things. The one option I haven't been able to do is install NetBEUI on the XP machine. It's new...there is a recovery disc but no XP disc, which you apparently need to install NETBEUI
Oh and the internet adaptor is like this.
Client for Microsoft Networks
File and printer sharing
Internet Protocol (TCP/IP) properties - obtain IP and DNS automatically. (I tried assigning IP...no ping either way from the XP) Disabled NetBios.
Hoping for some wise words in the morning...I'm outa here! :)
NetBeui often seems to have problems when working side by side with TCP/IP (which is required by internet sharing). I was asked to do the same thing a couple of years ago (XP/98) and finally got it working by removing NetBeui.
Years ago, NetBeui was quick and simple, but I gave up on it some years ago.
Kaled.
I used it for years myself, enjoying it's stability and security. I didn't even upgrade to XP Pro here until two years ago. But now, the only reason I even keep the 2000 disk is because I may find a use for it someday on a customer's machine or something.