![]() |
|
Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
|||||||
| Networking with Windows Vista Networking issues and questions with Windows Vista. (microsoft.public.windows.vista.networking_sharing) |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Network printer (Brother 2040 laser) is on an IOGear single-port wireless
print server. The whole setup worked at one time for both XP machines and the single Vista laptop I had at my previous home. Dismantled and reinstalled at new digs, the print server and printer work fine with my XP machines but not for my Vista laptop (a second Vista machine newly added to the network). The print queue returns an error message. Vista's file and print sharing and network discovery are on. The printer is on a port labeled LPT:PS3834-1, described as 192.168.1.160,PID:1. The print server is set up with a static IP at .160 and can be pinged. I tried putting the printer on the LPT1 port, with no joy. I would appreciate some suggestions for other things to try. Finally, I have to delete the test print files twice. After the failed test print, the queue message changes from "Printing" to "Error - printing." After I cancel the document the first time, the message changes to "Deleting - Error - printing" and then to "Error - Sent to printer." Canceling the document a second time finally gets rid of it in the queue. Is this expected behavior? |
|
|||
|
Did you install the printer driver?
"John Hoog" wrote in message ... Network printer (Brother 2040 laser) is on an IOGear single-port wireless print server. The whole setup worked at one time for both XP machines and the single Vista laptop I had at my previous home. Dismantled and reinstalled at new digs, the print server and printer work fine with my XP machines but not for my Vista laptop (a second Vista machine newly added to the network). The print queue returns an error message. Vista's file and print sharing and network discovery are on. The printer is on a port labeled LPT:PS3834-1, described as 192.168.1.160,PID:1. The print server is set up with a static IP at .160 and can be pinged. I tried putting the printer on the LPT1 port, with no joy. I would appreciate some suggestions for other things to try. Finally, I have to delete the test print files twice. After the failed test print, the queue message changes from "Printing" to "Error - printing." After I cancel the document the first time, the message changes to "Deleting - Error - printing" and then to "Error - Sent to printer." Canceling the document a second time finally gets rid of it in the queue. Is this expected behavior? |
|
|||
|
Yes I did.
"JerryM" wrote in message ... Did you install the printer driver? "John Hoog" wrote in message ... Network printer (Brother 2040 laser) is on an IOGear single-port wireless print server. The whole setup worked at one time for both XP machines and the single Vista laptop I had at my previous home. Dismantled and reinstalled at new digs, the print server and printer work fine with my XP machines but not for my Vista laptop (a second Vista machine newly added to the network). The print queue returns an error message. Vista's file and print sharing and network discovery are on. The printer is on a port labeled LPT:PS3834-1, described as 192.168.1.160,PID:1. The print server is set up with a static IP at .160 and can be pinged. I tried putting the printer on the LPT1 port, with no joy. I would appreciate some suggestions for other things to try. Finally, I have to delete the test print files twice. After the failed test print, the queue message changes from "Printing" to "Error - printing." After I cancel the document the first time, the message changes to "Deleting - Error - printing" and then to "Error - Sent to printer." Canceling the document a second time finally gets rid of it in the queue. Is this expected behavior? |
|
|||
|
John, in the Vista'a Network and Sharing, did you add the printer from
there(not just the Driver), and browse to find the Network Printer, then let windows install it? Also, a bit of Networking info below. http://technet.microsoft.com/en-us/l.../bb727037.aspx Have a read of the above link re Vista File and Printer Sharing. Permissions/Share info is there as well. If using Norton, McAfee, Trend Micro I.S., make sure file and printer sharing is enabled in THEIR firewall (or LAN allowed, depending on how their Exceptions are worded in their Firewall) 1st thing to do is make sure that the Workgroup Name of ALL the computers is the SAME. In Vista Network and Sharing: Network Discovery: ON (So it can see the other computers) Network set to Private (Public is for hotspots, airports, etc) File Sharing: ON Public Folder Sharing: ON (Vista’s Public Folder is the same as XP’s Shared Docs) Password Protected: OFF (unless you want to set up identical usernames and passwords (passwords can be different) on ALL computers in your Network) If you have it ON, you will be asked for a username and password when you try to access a Vista computer from an XP computer, or a Vista computer. Also, run the XP’s Home or Small Office Network File and Printer Sharing Wizard to include Vista in your “New” Network, even if you had an XP Network set up prior to adding a Vista computer to it(redoing the Wizard seems to work for XP machines!). In “My Network Places”: “Set up a Home or Small Office Network” OR under Accessories Communications Network Setup Wizard Allow File and Printer Sharing. -- Mick Murphy - Qld - Australia "John Hoog" wrote: Yes I did. "JerryM" wrote in message ... Did you install the printer driver? "John Hoog" wrote in message ... Network printer (Brother 2040 laser) is on an IOGear single-port wireless print server. The whole setup worked at one time for both XP machines and the single Vista laptop I had at my previous home. Dismantled and reinstalled at new digs, the print server and printer work fine with my XP machines but not for my Vista laptop (a second Vista machine newly added to the network). The print queue returns an error message. Vista's file and print sharing and network discovery are on. The printer is on a port labeled LPT:PS3834-1, described as 192.168.1.160,PID:1. The print server is set up with a static IP at .160 and can be pinged. I tried putting the printer on the LPT1 port, with no joy. I would appreciate some suggestions for other things to try. Finally, I have to delete the test print files twice. After the failed test print, the queue message changes from "Printing" to "Error - printing." After I cancel the document the first time, the message changes to "Deleting - Error - printing" and then to "Error - Sent to printer." Canceling the document a second time finally gets rid of it in the queue. Is this expected behavior? |
|
|||
|
Thanks, Mick. The answer's probably among those things you mentioned. I'll
get busy and check. "Mick Murphy" wrote in message ... John, in the Vista'a Network and Sharing, did you add the printer from there(not just the Driver), and browse to find the Network Printer, then let windows install it? Also, a bit of Networking info below. http://technet.microsoft.com/en-us/l.../bb727037.aspx Have a read of the above link re Vista File and Printer Sharing. Permissions/Share info is there as well. If using Norton, McAfee, Trend Micro I.S., make sure file and printer sharing is enabled in THEIR firewall (or LAN allowed, depending on how their Exceptions are worded in their Firewall) 1st thing to do is make sure that the Workgroup Name of ALL the computers is the SAME. In Vista Network and Sharing: Network Discovery: ON (So it can see the other computers) Network set to Private (Public is for hotspots, airports, etc) File Sharing: ON Public Folder Sharing: ON (Vista’s Public Folder is the same as XP’s Shared Docs) Password Protected: OFF (unless you want to set up identical usernames and passwords (passwords can be different) on ALL computers in your Network) If you have it ON, you will be asked for a username and password when you try to access a Vista computer from an XP computer, or a Vista computer. Also, run the XP’s Home or Small Office Network File and Printer Sharing Wizard to include Vista in your “New” Network, even if you had an XP Network set up prior to adding a Vista computer to it(redoing the Wizard seems to work for XP machines!). In “My Network Places”: “Set up a Home or Small Office Network” OR under Accessories Communications Network Setup Wizard Allow File and Printer Sharing. -- Mick Murphy - Qld - Australia "John Hoog" wrote: Yes I did. "JerryM" wrote in message ... Did you install the printer driver? "John Hoog" wrote in message ... Network printer (Brother 2040 laser) is on an IOGear single-port wireless print server. The whole setup worked at one time for both XP machines and the single Vista laptop I had at my previous home. Dismantled and reinstalled at new digs, the print server and printer work fine with my XP machines but not for my Vista laptop (a second Vista machine newly added to the network). The print queue returns an error message. Vista's file and print sharing and network discovery are on. The printer is on a port labeled LPT:PS3834-1, described as 192.168.1.160,PID:1. The print server is set up with a static IP at .160 and can be pinged. I tried putting the printer on the LPT1 port, with no joy. I would appreciate some suggestions for other things to try. Finally, I have to delete the test print files twice. After the failed test print, the queue message changes from "Printing" to "Error - printing." After I cancel the document the first time, the message changes to "Deleting - Error - printing" and then to "Error - Sent to printer." Canceling the document a second time finally gets rid of it in the queue. Is this expected behavior? |