Tip: File sharing Vista vs. Other systems

[DelJo63]

If you are using a firewall other than Windows Firewall, you must configure
the firewall to allow incoming network discovery and file and printer sharing traffic.

(1) For network discovery of other computers running Windows Vista,
you must allow the following incoming Transmission Control Protocol (TCP) and
User Datagram Protocol (UDP) traffic:

* UDP 3702
* TCP 5357
* TCP 5358​

(2) For network discovery of computers running Windows XP
and for file and printer sharing for both Windows Vista and Windows XP, you must allow the
following incoming traffic:

* UDP 137 netbios-name
* UDP 138 netbios-dgm
* TCP 139 netbios-ssn
* TCP 445 tcp sharing
​

(3) For network discovery of network devices, you must allow the following incoming traffic:

* UDP 1900 (the ssdp port)
* TCP 2869​

For more information about how to configure your third-party firewall to allow
incoming traffic, see the documentation for your third-party firewall.

Notice: (2) is the only mention of Print / File Sharing. These ports will enable P/FS
across many OS systems. Network discovery is no a prerequisite for P/FS

Vista firewalls have the special configuration option to make the port Private vs Public
and you need Private to access the shares on your LAN. Public is used to protect you at a Hotspot.

 

[kimsland]

Is this the same issue when users cannot set up their printer? (ie Not Found)

Should the user (in this case)

Setup the port to Private Network (default?)
Allow all TCP and UDP incomming and outgoing on all those ports (not default?)
Download the updated printer drivers
Then run the new printer network wizard
(Start -> Run ->rundll32 printui.dll,PrintUIEntry /il)

I have found information here as well on:
Windows Vista Print Management Step-by-Step Guide
Edit: (I went overboard, this page is Not relevant to my question)

But just wanted to know if this is the reason why Printers are not found
(Obviously confirming printer is attached and Print Spooler is running)

 

[DelJo63]

Windows has been supporting IPP since (at least) Windows 2000.
I have a entire Windows network where all printing is done using
IPP [CUPS] (and thus port 631). Works like a charm.

But, if you are using SMB Printing, then it
won't use port 631 but rather reverts to port 139/455

Windows actually supports various printing protocols, including
SMB, IPP, LPR, HP TCP/IP (JetDirect) along others.

edit:

port 515 LPD: Line Printer Daemon​

/edit

 

[kimsland]

Good point, my question is too open-ended

I'll keep those TCP & UDP ports information for reference.

Thank-you jobeard on another excellent Tip
I'm thinking it's write a book time, but very thankful to have this info at TechSpot

 

[DelJo63]

synergism: the sum of the parts is greater than the whole. :wave:

 

[DelJo63]

the VISTA Print Management stuff looks (to me) like it's Domain Controller specific and
not Standalone P/FS - home user friendly.

Pushing server devices to the clients is nice for the admin to avoid manual config of the
client systems, but print spooling will run nicely without this or the Device Discovery stuff noted above.

 

[gbhall]

Can you tell me if printer support in Vista has improved AT ALL over previous versions of OS.

For example, XP seems no different to Win98 in terms of (say) interrupting or cancelling a printout or restarting a printout. It is next to impossible to do this in a timely, responsive fashion, especially on inkjet printers.

 

[DelJo63]

hum; your question is entirely off the topic and specifically related to print spooling operations.

Please open a new thread for the subject and I am sure others will be interested in it