Annoyances.org
Home » Windows 2000 Discussion Forum » Message 1216303601 » Entire Thread Search | Help | Home
  
File and Print Sharing Delay
Showing all messages in thread #1216303601
Windows 2000 Annoyances Discussion Forum


The following are all of the messages in this thread (9 in all), shown in chronological order. Click any message subject to view that message by itself or to view the thread hierarchy.
File and Print Sharing Delay
Thursday, July 17, 2008 at 7:06 am
Posted by kkunzler (3 messages posted)

I have a windows 2000 server that is having difficulty connecting to a windows XP pro shared printer. It takes 53 seconds from the time the print job is sent to the time the small text file is printed. I ran wireshark and watched the traffic and I noticed that I get a SMB Tree connect AndX request to Path: \\[hostname]\IPC$ and then it hangs and at second 53 a new request comes through to connect to path: \\[hostname]\[printer]. Any ideas as to what could be causing this delay?

[Reply or follow-up to this message]

Tip: Run a free scan for common Windows errors ad

re: File and Print Sharing Delay
Thursday, July 17, 2008 at 10:48 am
Posted by geek9pm (906 messages posted)

No, I don't really know. But have you tried to un install and re install networking on both machines?
What printer are you using? (Yes, not all print drivers behave the same on the local network.)
Do both computers have same user names and passwords? Are you using a third-party firewall?
Do you think 53 seconds is not fast enough on a smalll network? That is near typical for some low-end printers.

Geek9pm

[Reply or follow-up to this message]

re: File and Print Sharing Delay
Thursday, July 17, 2008 at 12:00 pm
Posted by DEX (11819 messages posted)

Dealing with Unwanted Spyware and Parasites

Click Here



You may want to check the spooler command to make sure it's up and running in the background. Image and video hosting by TinyPic ==============

Are you a wood worker ?,if so Click Here


On Thursday, July 17, 2008 at 7:06 am, kkunzler wrote:
>I have a windows 2000 server that is having difficulty connecting to a windows XP
>pro shared printer. It takes 53 seconds from the time the print job is sent to the
>time the small text file is printed.
>
>I ran wireshark and watched the traffic and I noticed that I get a SMB Tree connect
>AndX request to Path: \\[hostname]\IPC$ and then it hangs and at second 53 a new
>request comes through to connect to path: \\[hostname]\[printer].
>
>Any ideas as to what could be causing this delay?
>

[Reply or follow-up to this message]

re: File and Print Sharing Delay
Thursday, July 17, 2008 at 12:59 pm
Posted by kkunzler (3 messages posted)

Geek9pm, The printer is actually a serial receipt printer shared by the local computer. 53 seconds is way to long to wait for a receipt to print. When I send a print job directly, it prints immediately. In fact, if I send a print job immediately following another print job, it print immediately. The 53 Seconds dely only occurs if their has not been a print job sent between the two computers for a while.

[Reply or follow-up to this message]

re: File and Print Sharing Delay
Thursday, July 17, 2008 at 1:50 pm
Posted by geek9pm (906 messages posted)

Ik, Pardon me. I thought it was a home network.
You have a specific need and it seems that XP is not keeping the network connection open for printer jobs.
If this were my problem in a commercial place, I would go for a quick and sure solution rather that trying understand what XP is doing.
Software solution:
Set up some kind of background task the starts a 'null' print job about once every minute or two. This could be a simple thing written in Visual Basic or C++ or whatever. A 'null' job would be just some characters that will not make the printer print, but wil force XP to start and finish a print job For most serial printers, the hex chars 00 and 7F just waste time and do not print. The printer may also have a reset sequence that could also be used to waste time and force XP to keep the connection.
Hardware fix:
You can do a serial printer wired directly with two computers with a hardware thing doing time share.

Geek9pm

[Reply or follow-up to this message]

re: File and Print Sharing Delay
Friday, July 18, 2008 at 3:52 pm
Posted by geek9pm (906 messages posted)

More info.
A search of the Microsoft KB gives lots of bad news.
query=SLOW+NETWORK+PRINT
Results 1-20 of 146 are sad. You can read the rest.

Geek9pm

[Reply or follow-up to this message]

re: File and Print Sharing Delay
Tuesday, July 22, 2008 at 5:53 am
Posted by outofpocket (210 messages posted)

Is the server running a DNS server?  If not and there's no DNS server on your network, 
look to see if the DNS client is running as a service on the W2000 server.  If it 
is, consider stopping it as a test to see if the access to printer is faster.  HTH
Outofpocket

[Reply or follow-up to this message]

re: File and Print Sharing Delay
Tuesday, July 22, 2008 at 6:16 am
Posted by kkunzler (3 messages posted)

Interestingly, I did some more testing a couple days ago. I moved the computer to a different part of the network, and the delay vanished, I then moved it back expecting the delay to return, but it didn't. I am now going on the 3rd full day without the delay (plus a weekend). I am curious to know what solved the problem, but it appears to have magically repaired itself.

[Reply or follow-up to this message]

re: File and Print Sharing Delay
Thursday, July 24, 2008 at 1:03 pm
Posted by geek9pm (906 messages posted)

Tell your Boss you did research on your own time and we have forbid you to reveal how we (the aggregate forum body) did this for you! It is a Professional Secret! If you don't tell, we won't tell!

Geek9pm

[Reply or follow-up to this message]

Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread
Return to the Windows 2000 Discussion Forum


All content at Annoyances.org is Copyright © 1995-2008 Creative Elementtm All rights reserved.
Please do not plagiarize; redistributing these pages without permission is strictly prohibited.