Ok, I have 3 machines set up on my network. 2 with 2K and one with 98. The 2k ones have the same net card in and the 98 one has a diferent one (they are all Realtek based). The problem that I have is as follows: 2k machines can see each other 98 machine can see the internet over the shared connection 98 machine cannot see other machines in group I reinstalled 98 and it saw both machines but now will not display either [/list=1] 98 machine has the followin in the properties: Client for Microsoft networks Dial-Up Adapter Realtek RTL8139/810x Family PCI Fast Ethernet NIC TCP/IP for Dial-Up and Realtek File sharing I have all default settings for the properties of each. Why is it not allowing me to see the other machines, or see it from the other machines, but still see the shared internet???? Meblin
what happens when you got run and type \\one of the 2k pcs name? i.e my machine is \\Herbie. Do you see the win 98 machine then?
I have used find to look for the machines on all 3 and I cannot see them. On the 2K machines I was getting "This is not a valid path" type error. I though I could over come the problem, 1st time around, by formating C: and installing 2K. However, when I started to install it crashed out just when it had finished loading the files necessary to install. It said to run chkdsk /f. I could only find a crappy boot disk so just put 98 back on. This seemed to solve the problem but now its gone belly up again Meblin
In that case add netbeui to the protocols in both 2k and 98 and make that the prefered protocol (I aint done this for years so im going from the top of my head). Although they say 2k hasn't got netbeui (bios) it has. Then see if that works. Also if you have a firewall on each machine try disabling them for the time being.
Using multiple protocols works, but isn't your best bet...If you're still interested in screwing around with this, here's a couple of questions for you: 1) Can MachineA PING MachineB using the IP Address? if so, 2) Can MachineA PING MachineB using the name? 3) Are you using DHCP of some sort, or are the IPs static? Consider using a HOSTS file for name resolution if question 1 is true, and 2 isn't. In my experience, once you've found a machine through a ping, it ends up storing that information in it's nbtstat table, and will generally show up in your network neighborhood. Give that stuff a try and let me know what happens!
Here's one for you: 2 PCs : 1) "Daisy" - Windows XP 2) "Peach" - Windows 98 They are both hooked up to a router which supplies them both with a cable connection. Peach can ping Daisy and Router Daisy can ping Peach and Router Peach can see "workgroup" and herself in it. Daisy cannot see "workgroup" and thus cannot see herself in it. I have an Apache server on Peach which Daisy can see. I have tweaked and messed and blahed but to no avail. What am I doing wrong?
Yeah, WinXP is a little funny that way. I have experienced the same problems workgrouping XP with 9x. It seems like MS pretty much designed it for domains, and that's about it. Anyway, a quick little troubleshooting test... On "Daisy" if you go Start>Run and enter "\\peach" does anythihng come up? If not, go to a CMD prompt and type: "ping -a xxx.xxx.xxx.xxx" (daisy's IP address). The -a will resolve the name of the IP you give it. At this point, you computer will have stored the name Daisy and the corrosponding IP. You should be able to successfully do the first test, and I would bet that all of a sudden your workgroup is working fine. My fix for this problem (as quick and dirty as it might be) is to map a network drive from each machine to the other machine, using the IP address (i.e: net use j: \\xxx.xxx.xxx.xxx /p:y) The p makes the connection persistent, so it will always come back after a reboot...but this only works on the XP machine. You could probably also write a hosts file (as I mentioned in my last post), but I haven't ever tested to see if that works in this situation. Hope that helps, let me know if it doesn't!
