network printer doesn't always work

I have a crossover network, server on win2000pro, client on win89SE. I can share files no probs and i have a network printer set up. Some days when i print from client it works, other days it doesnt. Main problems are: 1)The print job gets sent, but it shows up in the server as already printed when it hasnt printed. 2)I get asked for a password to access printer when i didnt set one in the first place 3)The print job gets sent but never even shows up in the server print properties. -- When i reboot both machines the connection comes up good, but then the next day if i've shut down the client only and start up again , i get the same problems again. Really annoying as i'm pretty sure all my protocols, settings etc are correct
Please help or advise me. I spend more time trying to get the things running than actually use them.

 

Make sure you have the right printer drivers for both machines.
Make sure you have the right printer drivers for both machines.

A lot of people who like to print web pages (for some reason I can't fathom) have difficulties with their printers and specifically printers on Windows 98. Apparently, some characters in some web pages look like control codes to some printers--and hang the printer.

Windows 98 print spooler isn't very robust. If the spooler hands, you'll need to reboot.

If the shared printer employes a spooler on the 2k machine, try stopping and starting the spooler service on the 2k machine.

Do you check to see if the printer shows up as a share before trying to print? Maybe a browser problem. Use LMHosts (unless you are using ICS's DHCP) to prejudice finding the 2kPro machine.

How are you logged on? READ THIS...

 

thanks bitbyter, big help!! only things im not sure about is stopping and starting spooler on 2k, and using LM host (dont know what that means?) Yes i do print web pages from 98SE to 2K, and use protocol NetBUEI. Log on article was a help. Thanks

 

The spooler is a service.

Start~Run~Settings~Control Panel~Administrative Tools~Computer Management~Services and Applications~Services...and highlight Print Spooler, right-click and pick Stop or Start from the context menu.

Starting or stopping some services will hang your system.

Why are you using NetBEUI?

I know it gets suggested some places, and sometimes for a specific reason. I can only tell you that I've run TCP/IP, only, for the last 5 years, and there's no network problem that requires NetBEUI as a solution. There is the practice of binding F&PS only to NetBEUI for security... ...for which security, I have always preferred using a firewall and/or router with NAT.

But that's only my opinion. This information may be interesting.

If you are using TCP/IP only on your LAN, as I am, and if your LAN is small enough (typically not more than a dozen nodes or so), then LMHOSTS might be of interest.

LMHOSTS is a file similar to the HOSTS file except that where HOSTS resolves FQDN's to IP address, LMHOSTS resolves NetBIOS names to IP address.

Do a search on your systems for LMHOSTS*.* Depending on the OS, you should find something in C:\winnt\system32\drivers\etc\ or C:\WINDOWS or C:\windows\system32\drivers\etc\ or wherever \etc\ is.

Anything with a .sam extension is a sample file. Both LMHOSTS and HOSTS have no filename extension. Use a text editor to modify them.

LMHOSTS is similar in format to HOSTS.

# Sample lmhosts file.
#
127.0.0.1 localhost
192.168.1.1 thegateway
192.168.1.3 myownpc
192.168.1.4 myotherpc

Here's four entries for an LMHOSTS file. Your addresses and computer names will vary. The IP addresses must be fixed -- manually assigned. If you are using DHCP and the addresses are not reserved for specific systems, then LMHOSTS might confuse the network.

Name Resolution is essential to the process of one host finding shared resources on another host. Regardless of the protocol. Windows 2000 is geared towards TCP/IP.

LMHOSTS Info from Microsoft...

Network Neighborhood (and equivalents) are the gui interface for the network browser (not the same as a web browser). If a host on a Windows network offers services to other nodes, then the host should show up in the network browser. If a host does not offer services to other nodes on the network, then it will not show up in the network browser. If a host does offer services and does not show up in the browser, there is either a problem with the network browser or a name resolution problem... ...for whatever protocol.

The W2k machine has the printer that is shared? If you have the choice, make sure that machine is turned on first. Under F&PS config, make the W2K machine be the Browse Master on the Advanced tab.

When you install both protocols on each computer and set Netbeui as the first protocol to be used, Windows uses Netbeui for the communication between Windows computers within the LAN segment and uses TCP/IP for communication across routers and to other parts of your WAN. You won't use LMHOSTS in this case.

You should not have NetBEUI bound to your dial-up interface.

If you have both protocols installed, unbind F&PS as well as Client for Microsoft Networks from TCP/IP for the dial-up interface.

Disable NetBIOS over TCP/IP by going to TCP/IP properties, click the advanced button and go to the WINS tab. Click on Disable NetBIOS over TCP/IP.

Keep notes on what you do (EVERY step) so you can un-do if necessary.

The big problem with shares is no password and/or no permissions restrictions.

 

Thanks dude, you're a legend!!