We have Win98se workstations on a Novell 4.2 network. A printer attached to a workstation is shared on the network. A computer that has been printing to this printer for a year suddenly cannot. The computer that has the printer shows up in network neighborhood, but when clicked get the message "\\Lwalsh not accessible. This device does not exist on the network". This computer can read drives and printers on all other computers. No other computers on the network are having this problem. No programs or updates have been added to either computer. Any ideas? Thanks.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Shared printer not accessible 1
- Thread starter dfb627
- Start date
-
1
- #2
mattjurado
MIS
So other computers can print fine to this printer?
If so, post some more details...
Are you running tcp/ip or netbeui?
Static IPs?
Matt J.
Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.
If so, post some more details...
Are you running tcp/ip or netbeui?
Static IPs?
Matt J.
Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.
- Thread starter
- #3
mattjurado
MIS
Couple of things you might try...
1. Reinstall TCP/IP on the workstation having the problem. Remove it, reboot, put it back, reboot, try again.
2. Create an lmhosts file with an ip entry for the computer you are trying to access, mapped to its netbios name.
Matt J.
Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.
1. Reinstall TCP/IP on the workstation having the problem. Remove it, reboot, put it back, reboot, try again.
2. Create an lmhosts file with an ip entry for the computer you are trying to access, mapped to its netbios name.
Matt J.
Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.
- Thread starter
- #5
mattjurado
MIS
Which was it, corrupt TCP/IP?
Matt J.
Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.
Matt J.
Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.
- Thread starter
- #7
mattjurado
MIS
You're welcome.
Matt J.
Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.
Matt J.
Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.
- Status
