RE: Printing from Win9x clients stops
- From: "DaveR" <DaveR@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 2 Jun 2005 08:54:05 -0700
Hello Nathan,
We had applied the SMB signing changes already, this was as a result of
perceived "slow network transfers" (as per smallbizserver.net).
However, I re-checked the settings and followed your advice re. gpudate
/force.
I then re-started two of the ME machines. No difference.
I then wrote the lmhosts file and re-started (again two machines) - again,
no difference.
Any further suggestions greatly appreciated!
Dave
"Nathan Liu [MSFT]" wrote:
> Hello Dave,
>
> Thank you for your update.
>
> Based on my research, since this issue only occurs on all Windows 9x
> workstations, this should be an SMB signing issue. We should disable the
> SMB Signing on the SBS server. Please try to perform the following steps:
>
> 1. Open Server Management Console, expand Advanced Management -> Group
> Policy Management -> DomainName.local.
>
> 2. Right-click Default Domain Policy and select Edit.
>
> 3. Open the Computer Configuration\Windows Settings\Security
> Settings\Local Policies\Security Options folder.
>
> 4. Locate the Microsoft network server: Digitally sign communications
> (always) policy setting, and then click Disabled or Do Not Configure.
>
> Also do the same steps to disable the SMB signing policy in the Default
> Domain Controller Policy. After you finish that, please run "gpupdate
> /force" at the SBS Server.
> Please also run "gpupdate /force" at the client side or restart it to
> update the group policy.
>
> For detailed information, please refer to the KB article 811497.
>
> 811497 Error Message When Windows 95 or Windows NT 4.0 Client Logs On to
> Windows Server 2003 Domain
> http://support.microsoft.com/?id=811497
>
> Otherwise, if the issue persists, please try to perform the resolution in
> the KB article 180094.
>
> 180094 How to write an Lmhosts file for domain validation and other name
> resolution issues
> http://support.microsoft.com/kb/180094/en-us
>
> I'm looking forward to your update. If you have any questions or concerns,
> please do not hesitate to let me know. I am always happy to be of further
> assistance.
>
> Best regards,
>
> Nathan Liu (MSFT)
> Microsoft CSS Online Newsgroup Support
> Get Secure! - www.microsoft.com/security
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --------------------
> >Thread-Topic: Printing from Win9x clients stops
> >thread-index: AcVmyAO0vMDq1/BgRtqC5o6kEJEXyg==
> >X-WBNR-Posting-Host: 83.104.120.89
> >From: "=?Utf-8?B?RGF2ZVI=?=" <DaveR@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >References: <451C05BA-43DA-436F-A3CC-1A7485336799@xxxxxxxxxxxxx>
> <gAkUl#PZFHA.2184@xxxxxxxxxxxxxxxxxxxxx>
> >Subject: RE: Printing from Win9x clients stops
> >Date: Wed, 1 Jun 2005 09:36:09 -0700
> >Lines: 175
> >Message-ID: <CEE9A710-4801-4C3D-B75B-025ECC2B9FD4@xxxxxxxxxxxxx>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.windows.server.sbs
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:123329
> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >
> >Hello Nathan, herewith the results:
> >
> >> 1. Please open the system Event Viewer on the problematic clients, and
> >> check whether there are any error messages about this issue, then paste
> the
> >> full context in your reply post.
> >
> >I don't know where to look in Windows Me, I can find no relevent log files
> >either.
> >
> >>
> >> 2. Please disable the eTrust Gateway and Pest Patrol program on the SBS
> >> Server, then try again. Please check whether the issue can be
> re-produced.
> >> If the issue is resolved, please contact your third-party software
> vendor
> >> and make sure this software does not interfere with SBS Server.
> >
> >Gateway removed, Pestpatrol disabled
> >
> >>
> >> 3. If you installed any third-party Anti-Virus software on the
> problematic
> >> clients, please disable it and try again. Please also check whether the
> >> issue can be re-produced. If the issue is resolved, please contact your
> >> third-party software vendor and make sure this software does not
> interfere
> >> with SBS Server.
> >
> >Local virus scanner disabled
> >
> >>
> >> 4. If the issue persists, please manually re-join the windows 9x clients
> >> into the SBS Server Domain, then try again. Please check whether the
> issue
> >> can be re-produced.
> >
> >Two separate machines removed from the Domain and re-joined
> >
> >>
> >> 5. Otherwise, please try to perform the following testing steps:
> >>
> >> a. Verify basic network connectivity.
> >>
> >> Check user rights, protocols, share names, and so on to determine if
> >> you can see the server. Copy files to a share on the print server using
> >> Windows Explorer. If you cannot access the server, you may not be able
> to
> >> access the printer.
> >
> >All other networked services, files sharing, mail, IE etc OK, only
> printing
> >affected.
> >
> >>
> >> b. Create a local printer and redirect the port to the network
> server.
> >>
> >> Create a local printer and in the Ports section, create a new port.
> >> Click Local, and type the server and printer name for the printer (use
> the
> >> \\servername\printername syntax). Use this port for the local printer.
> This
> >> determines whether there is a problem with the copying of files from the
> >> server to the workstation that occurs when you use a Connect To Setup or
> >> click Network Printer in the Add Printer Wizard.
> >
> >Done all the above, have also removed and re-installed several networked
> >printers from client machines and added networked printers previously not
> >install to some.
> >
> >>
> >> c. Printing from an MS-DOS-based program.
> >>
> >> Make sure that the NET USE command has been run to map the LPT port
> to
> >> the network share. If it has, delete it and re-map the port. If it then
> >> works, there may be an issue with ghosted connections. A command may
> need
> >> to be run in the login script to remap the port each time you log on.
> >
> >Have deleted and re-mapped ports
> >
> >>
> >> If it is still not printing, try typing "dir > LPT<x>" (without
> >> quotation marks) where <x> is the number of the port being mapped. If it
> >> still does not print, double-check the networking.
> >
> >"Access denied" - do we have a key here? As above all other network
> >function are fine.
> >
> >>
> >> d. If you are using LPR or printing to a JetDirect card using the
> >> TCP/IP protocol, try these items:
> >>
> >> - Ping the IP address. If it fails, check the network connectivity
> and
> >> verify IP addresses.
> >>
> >> - Create an LPR port to the printer and then create a local printer
> >> connected to that port. This is the recommended way to connect to a
> >> JetDirect printer. Sharing this printer on the network allows the
> computer
> >> to act as a print queue for the JetDirect printer.
> >
> >All above is N/A, we are looking at 2xHP5000n, 2x HP750C A0 plotters,
> >1xCanon 5000i mutlifunction, all installed via TCP/IP ports on the server
> and
> >this system has worked flawlessly for over a year to date.
> >
> >>
> >> e. Determine whether you can print locally.
> >>
> >> If possible, try printing locally. This determines whether it is a
> >> network or computer-specific problem.
> >
> >No trouble printing locally, and I re-iterate we have 11 XP machines
> working
> >perfectly and 12 ME machines which all failed at the same time, it does
> not
> >seem to be a machine local problem.
> >
> >Do we have a situation where somehow ME machines are denied access
> somewhere
> >in Group Policy?
> >
> >Looking forward to any other suggestions you may have!
> >And thanks very much for your time so far - Dave
> >
> >>
> >> To get additional detailed information, you may refer to the RESOLUTION
> of
> >> the following KB article:
> >>
> >> 314073 How to troubleshoot network printing problems in Windows XP
> >> http://support.microsoft.com/kb/314073/en-us
> >>
> >> 163551 Troubleshooting Printing Problems in Windows
> >> http://support.microsoft.com/?id=163551
> >>
> >> I'm looking forward to your update. If you have any questions or
> concerns,
> >> please do not hesitate to let me know. I am always happy to be of
> further
> >> assistance.
> >>
> >> Best regards,
> >>
> >> Nathan Liu (MSFT)
> >> Microsoft CSS Online Newsgroup Support
> >> Get Secure! - www.microsoft.com/security
> >> =====================================================
> >> When responding to posts, please "Reply to Group" via your newsreader so
> >> that others may learn and benefit from your issue.
> >> =====================================================
> >> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >>
> >> --------------------
> >> >Thread-Topic: Printing from Win9x clients stops
> >> >thread-index: AcVikqbQN3+rf9UFThytQeDo1ETV/Q==
> >> >X-WBNR-Posting-Host: 83.104.120.90
> >> >From: "=?Utf-8?B?RGF2ZVI=?=" <DaveR@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >> >Subject: Printing from Win9x clients stops
> >> >Date: Fri, 27 May 2005 01:04:05 -0700
> >> >Lines: 12
> >> >Message-ID: <451C05BA-43DA-436F-A3CC-1A7485336799@xxxxxxxxxxxxx>
> >> >MIME-Version: 1.0
> >> >Content-Type: text/plain;
> >> > charset="Utf-8"
> >> >Content-Transfer-Encoding: 7bit
> >> >X-Newsreader: Microsoft CDO for Windows 2000
> >> >Content-Class: urn:content-classes:message
> >> >Importance: normal
> >> >Priority: normal
> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >> >Newsgroups: microsoft.public.windows.server.sbs
> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:122146
> >> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >> >
> >> >Following a server reboot (to install aTrust Gateway and Pest Patrol)
> all
> >> >win9x clients are seeing:
> >> >There was an error writing to \\server\printer\ (printer):
> >> >There was a problem printing to the printer due to an unknown system
> error.
> >> >Restart Windows, and then try printing again.
> >> >This printer will be set to offline.
> >> >To save your print job in the local printer queue, click OK.
> >> >
> >> >All XP clients (11) are working perfectly! All win9x (12) show the
> same.
> >> >Printer drivers have been re-loaded on a client and one of the printers
> >> has
> >> >been re-installed on the server but to no avail.
> >> >Any ideas please.
> >> >
> >>
> >>
> >
>
>
.
- Follow-Ups:
- RE: Printing from Win9x clients stops
- From: Nathan Liu [MSFT]
- RE: Printing from Win9x clients stops
- References:
- RE: Printing from Win9x clients stops
- From: DaveR
- RE: Printing from Win9x clients stops
- From: Nathan Liu [MSFT]
- RE: Printing from Win9x clients stops
- Prev by Date: Re: Setting up Win2k3 on existing infrastructure
- Next by Date: Announcments in Companyweb
- Previous by thread: RE: Printing from Win9x clients stops
- Next by thread: RE: Printing from Win9x clients stops
- Index(es):
Relevant Pages
|
