My Windows XP Pro install had been working fine. In the last couple of days I noticed I can not print to the printer on my other PC that is sharing it via Windows.
I checked the NET VIEW command and of course I cant see any computers at all now. I have tried changing the computer name and workgroup and return it to the normal setting but nothing ever shows in NET VIEW. Of course the Microsoft client and File and Print is installed but something has gone bad.
The NET VIEW command just returns: There are no entries in the list, but I know there are 2 other machines in this workgroup and other other computers are fine. All other networking items are working fine and I can get to a local FTP server and to the Internet.
I noticed from IPCONFIG that NETBIOS over TCPIP is disabled but I have not changed anything. There is the default setting which is current and then enabled and disabled. I changed it to enabled and nothing, rebooted and nothing - still shows as disabled. So it appears to be stuck on disabled and thus MS file and print will not work.
Anyone have any ideas on how to fix this issue?
Thanks,
Greg
I checked the NET VIEW command and of course I cant see any computers at all now. I have tried changing the computer name and workgroup and return it to the normal setting but nothing ever shows in NET VIEW. Of course the Microsoft client and File and Print is installed but something has gone bad.
The NET VIEW command just returns: There are no entries in the list, but I know there are 2 other machines in this workgroup and other other computers are fine. All other networking items are working fine and I can get to a local FTP server and to the Internet.
I noticed from IPCONFIG that NETBIOS over TCPIP is disabled but I have not changed anything. There is the default setting which is current and then enabled and disabled. I changed it to enabled and nothing, rebooted and nothing - still shows as disabled. So it appears to be stuck on disabled and thus MS file and print will not work.
Anyone have any ideas on how to fix this issue?
Thanks,
Greg