Windows xp can/x27t access workgroup

Then go to the printer mftr. Install them on the target machine s. The printer should be seen during the installation routine. If it is not, install the drivers and then use the Add Printer Wizard. In some instances, certain printers need to be installed as Local printers but that is outside of this response. Was this reply helpful? Yes No. Sorry this didn't help. InstallSafe InstallSafe support. Disk Reviver Disk Reviver support. Security Reviver Security Reviver support. Privacy Reviver Privacy Reviver support.

MacReviver MacReviver support. Registry Reviver Registry Reviver support. Battery Optimizer Battery Optimizer support. Visit our Support Home page. Contact our Support Team. About Us Learn about ReviverSoft.

Trust The importance of trust. Testimonials What others are saying. Feedback How we are doing? I enabled that and now it doesn't give me a error it just is empty on the xp computers. I have the built in firewall on both xp computers disabled.

I did, just doesn't give me a error now, now on the xp computers the workgroups are empty. Have you disable winxp firewall. If not click on my computer icon and click on c:drive or folder and share it. I had the same problem. I had previously switched some things off for a bit more speed.

I could surf the net but not the LAN. All of the windows 7 machines on the network that are on or off the domain can access the server shares without issue. All of the Windows XP machines we have are not on the domain for various reasons. I have disabled windows firewall, antivirus, done a system restore on one, restarted the workstations, flushed DNS, reregistered DNS, refreshed IP's, and so forth.

This issue started today, yesterday everything was fine. The server rebooted last night, and one update was installed. It was Security Update kb I removed the update and the issue still occurs.

Could be that the server needs a reboot, but I am unable to reboot it during business hours. Something I have noticed, when pinging server from the XP machines, it is coming up with x. The server has four NIC's, but I don't see how that would cause a problem. When doing an nslookup it shows as the correct. Might be an issue with SMB 2. XP doesn't use it can't use it, in fact , but Windows 7 and Server use it by default.

I've also seen several instances where pending reboots do interfere with network communication, though in those instances it's not OS-specific.