connecting to XP network to access printer

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help
Post Reply
fasta6
Level 1
Level 1
Posts: 6
Joined: Wed Aug 05, 2009 12:06 pm

connecting to XP network to access printer

Post by fasta6 » Wed Aug 05, 2009 12:11 pm

I'm running Gloria on a desktop and I'm trying to get it to see the printer on an XP machine on my network. I can see the windows network but it won't open the network. I'm in the area to add a printer but it doesn't find one.

I'm new at this so it's probably simple, thanks.

altair4
Level 19
Level 19
Posts: 9751
Joined: Tue Feb 03, 2009 10:27 am

Re: connecting to XP network to access printer

Post by altair4 » Wed Aug 05, 2009 12:21 pm

From Network Printing: http://forums.linuxmint.com/viewtopic.php?f=42&t=28397
[] CONNECTING TO A WINDOWS PRINTER FROM LINUX

On WinXP: Make sure the printer is "shared"

Start > Control Panel > Printers and Faxes > right click on your printer > Sharing

[If you have already shared a folder or a drive, printer sharing is already activated. If not
then a new window appears and you must first enable remote access. To do so click the
security warning message ( not the Network Setup Wizard - please not the Network
Setup Wizard) , then the "Just enable printer sharing" button on the following screen]

check "Share this Printer"
Share Name: WinPrinter or whatever you choose

On Linux:


Menu > Administration > Printing > New > Windows Printer via Samba > Browse.
It should find it automatically after it does a network scan.

If it can't find anything you may have to fill in the dialog box, examples:
smb://WORKGROUP_NAME/MACHINE_NAME/WinPrinter
smb://MACHINE_NAME/WinPrinter
smb://192.168.0.100/WinPrinter

Note: Linux has a hard time with machine name resolution so you might be forced to use the IP
Address instead.

[It should then connect and you'll be asked about what make and model and such.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.

fasta6
Level 1
Level 1
Posts: 6
Joined: Wed Aug 05, 2009 12:06 pm

Re: connecting to XP network to access printer

Post by fasta6 » Thu Aug 06, 2009 1:45 pm

I tried what was suggested above, the printer is shared and I tried it with the PC name and path, no luck. No luck with the IP either.

Any more ideas?

altair4
Level 19
Level 19
Posts: 9751
Joined: Tue Feb 03, 2009 10:27 am

Re: connecting to XP network to access printer

Post by altair4 » Thu Aug 06, 2009 1:53 pm

We need more info I'm afraid,

In Mint:

Open Terminal
Type smbtree
Type findsmb
Type nmap -sT 192.168.0.100/22
Change 192.168.0.100 to the ip address of the Mint machine

Post the output please
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.

fasta6
Level 1
Level 1
Posts: 6
Joined: Wed Aug 05, 2009 12:06 pm

Re: connecting to XP network to access printer

Post by fasta6 » Thu Aug 06, 2009 5:40 pm

_________________________________________
/ You worry too much about your job. Stop \
\ it. You are not paid enough to worry. /
-----------------------------------------
\
\ \_\_ _/_/
\ \__/
(oo)\_______
(__)\ )\/\
||----w |
|| ||
lockhart@kitchen ~ $ smbtree
Password:
HOME
\\TVROOM TVroom
findsmbtimeout connecting to 67.63.55.33:445
timeout connecting to 67.63.55.33:139
cli_start_connection: failed to connect to TVROOM<20> (0.0.0.0). Error NT_STATUS_ACCESS_DENIED
\\KITCHEN kitchen server (Samba, LinuxMint)
\\KITCHEN\Print_to_PDF Print to a PDF File
\\KITCHEN\IPC$ IPC Service (kitchen server (Samba, LinuxMint))
\\KITCHEN\print$ Printer Drivers
lockhart@kitchen ~ $ findsmb

*=DMB
+=LMB
IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
---------------------------------------------------------------------
192.168.1.103 KITCHEN [KITCHEN] [Unix] [Samba 3.3.2]
lockhart@kitchen ~ $ nmap -sT 192.168.1.103/22
The program 'nmap' is currently not installed. You can install it by typing:
sudo apt-get install nmap
bash: nmap: command not found
lockhart@kitchen ~ $ sudo apt-get install nmap
[sudo] password for lockhart:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
nmap
0 upgraded, 1 newly installed, 0 to remove and 201 not upgraded.
Need to get 1187kB of archives.
After this operation, 4502kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
nmap
Authentication warning overridden.
Get:1 http://archive.ubuntu.com jaunty/main nmap 4.76-0ubuntu4 [1187kB]
Fetched 1187kB in 2s (551kB/s)
Selecting previously deselected package nmap.
(Reading database ... 107769 files and directories currently installed.)
Unpacking nmap (from .../nmap_4.76-0ubuntu4_i386.deb) ...
Processing triggers for man-db ...
Setting up nmap (4.76-0ubuntu4) ...

lockhart@kitchen ~ $ findsmb

*=DMB
+=LMB
IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
---------------------------------------------------------------------
192.168.1.103 KITCHEN [KITCHEN] [Unix] [Samba 3.3.2]
lockhart@kitchen ~ $ nmap -sT 192.168.1.103/22

Starting Nmap 4.76 ( http://nmap.org ) at 2009-08-06 16:35 CDT
All 1000 scanned ports on 192.168.0.13 are closed

All 1000 scanned ports on 192.168.0.14 are closed

All 1000 scanned ports on 192.168.0.41 are closed

All 1000 scanned ports on 192.168.0.42 are closed

All 1000 scanned ports on 192.168.0.69 are closed

All 1000 scanned ports on 192.168.0.70 are closed

All 1000 scanned ports on 192.168.0.110 are closed

All 1000 scanned ports on 192.168.0.111 are closed

All 1000 scanned ports on 192.168.0.153 are closed

All 1000 scanned ports on 192.168.0.154 are closed

All 1000 scanned ports on 192.168.0.179 are closed

All 1000 scanned ports on 192.168.0.180 are closed

All 1000 scanned ports on 192.168.0.182 are closed

All 1000 scanned ports on 192.168.0.193 are closed

All 1000 scanned ports on 192.168.0.221 are closed

All 1000 scanned ports on 192.168.0.222 are closed

All 1000 scanned ports on 192.168.0.237 are closed

All 1000 scanned ports on 192.168.0.238 are closed

All 1000 scanned ports on 192.168.0.251 are closed

All 1000 scanned ports on 192.168.0.252 are closed

All 1000 scanned ports on 192.168.1.1 are filtered

Interesting ports on 192.168.1.103:
Not shown: 998 closed ports
PORT STATE SERVICE
139/tcp open netbios-ssn
445/tcp open microsoft-ds

All 1000 scanned ports on 192.168.2.9 are closed

All 1000 scanned ports on 192.168.2.10 are closed

All 1000 scanned ports on 192.168.2.13 are closed

All 1000 scanned ports on 192.168.2.14 are closed

All 1000 scanned ports on 192.168.2.31 are closed

All 1000 scanned ports on 192.168.2.32 are closed

All 1000 scanned ports on 192.168.2.33 are closed

All 1000 scanned ports on 192.168.2.34 are closed

All 1000 scanned ports on 192.168.2.35 are closed

All 1000 scanned ports on 192.168.2.36 are closed

All 1000 scanned ports on 192.168.2.37 are closed

All 1000 scanned ports on 192.168.2.38 are closed

All 1000 scanned ports on 192.168.2.39 are closed

All 1000 scanned ports on 192.168.2.40 are closed

All 1000 scanned ports on 192.168.2.41 are closed

All 1000 scanned ports on 192.168.2.42 are closed

All 1000 scanned ports on 192.168.2.46 are closed

All 1000 scanned ports on 192.168.2.47 are closed

All 1000 scanned ports on 192.168.2.48 are closed

All 1000 scanned ports on 192.168.2.49 are closed

All 1000 scanned ports on 192.168.2.50 are closed

All 1000 scanned ports on 192.168.2.51 are closed

All 1000 scanned ports on 192.168.2.52 are closed

All 1000 scanned ports on 192.168.2.53 are closed

All 1000 scanned ports on 192.168.2.54 are closed

All 1000 scanned ports on 192.168.2.55 are closed

All 1000 scanned ports on 192.168.2.56 are closed

All 1000 scanned ports on 192.168.2.57 are closed

All 1000 scanned ports on 192.168.2.59 are closed

All 1000 scanned ports on 192.168.2.60 are closed

All 1000 scanned ports on 192.168.2.62 are closed

All 1000 scanned ports on 192.168.2.63 are closed

All 1000 scanned ports on 192.168.2.65 are closed

All 1000 scanned ports on 192.168.2.66 are closed

All 1000 scanned ports on 192.168.2.67 are closed

All 1000 scanned ports on 192.168.2.68 are closed

All 1000 scanned ports on 192.168.2.88 are closed

All 1000 scanned ports on 192.168.2.89 are closed

All 1000 scanned ports on 192.168.2.100 are closed

All 1000 scanned ports on 192.168.2.101 are closed

All 1000 scanned ports on 192.168.2.128 are closed

All 1000 scanned ports on 192.168.2.129 are closed

All 1000 scanned ports on 192.168.2.132 are closed

All 1000 scanned ports on 192.168.2.133 are closed

All 1000 scanned ports on 192.168.2.134 are closed

All 1000 scanned ports on 192.168.2.135 are closed

All 1000 scanned ports on 192.168.2.137 are closed

All 1000 scanned ports on 192.168.2.138 are closed

All 1000 scanned ports on 192.168.2.139 are closed

All 1000 scanned ports on 192.168.2.140 are closed

All 1000 scanned ports on 192.168.2.149 are closed

All 1000 scanned ports on 192.168.2.150 are closed

All 1000 scanned ports on 192.168.2.158 are closed

All 1000 scanned ports on 192.168.2.159 are closed

All 1000 scanned ports on 192.168.2.160 are closed

All 1000 scanned ports on 192.168.2.161 are closed

All 1000 scanned ports on 192.168.2.162 are closed

All 1000 scanned ports on 192.168.2.171 are closed

All 1000 scanned ports on 192.168.2.172 are closed

All 1000 scanned ports on 192.168.2.180 are closed

All 1000 scanned ports on 192.168.2.181 are closed

All 1000 scanned ports on 192.168.2.186 are closed

All 1000 scanned ports on 192.168.2.187 are closed

All 1000 scanned ports on 192.168.2.189 are closed

All 1000 scanned ports on 192.168.2.190 are closed

All 1000 scanned ports on 192.168.2.220 are closed

All 1000 scanned ports on 192.168.2.221 are closed

All 1000 scanned ports on 192.168.3.8 are closed

All 1000 scanned ports on 192.168.3.9 are closed

All 1000 scanned ports on 192.168.3.13 are closed

All 1000 scanned ports on 192.168.3.14 are closed

All 1000 scanned ports on 192.168.3.24 are closed

All 1000 scanned ports on 192.168.3.26 are closed

All 1000 scanned ports on 192.168.3.27 are closed

All 1000 scanned ports on 192.168.3.34 are closed

All 1000 scanned ports on 192.168.3.35 are closed

All 1000 scanned ports on 192.168.3.36 are closed

All 1000 scanned ports on 192.168.3.37 are closed

All 1000 scanned ports on 192.168.3.38 are closed

All 1000 scanned ports on 192.168.3.39 are closed

All 1000 scanned ports on 192.168.3.40 are closed

All 1000 scanned ports on 192.168.3.41 are closed

All 1000 scanned ports on 192.168.3.42 are closed

All 1000 scanned ports on 192.168.3.43 are closed

All 1000 scanned ports on 192.168.3.44 are closed

All 1000 scanned ports on 192.168.3.45 are closed

All 1000 scanned ports on 192.168.3.46 are closed

All 1000 scanned ports on 192.168.3.47 are closed

All 1000 scanned ports on 192.168.3.48 are closed

All 1000 scanned ports on 192.168.3.49 are closed

All 1000 scanned ports on 192.168.3.50 are closed

All 1000 scanned ports on 192.168.3.51 are closed

All 1000 scanned ports on 192.168.3.52 are closed

All 1000 scanned ports on 192.168.3.53 are closed

All 1000 scanned ports on 192.168.3.54 are closed

All 1000 scanned ports on 192.168.3.55 are closed

All 1000 scanned ports on 192.168.3.56 are closed

All 1000 scanned ports on 192.168.3.57 are closed

All 1000 scanned ports on 192.168.3.58 are closed

All 1000 scanned ports on 192.168.3.59 are closed

All 1000 scanned ports on 192.168.3.60 are closed

All 1000 scanned ports on 192.168.3.61 are closed

All 1000 scanned ports on 192.168.3.62 are closed

All 1000 scanned ports on 192.168.3.63 are closed

All 1000 scanned ports on 192.168.3.64 are closed

All 1000 scanned ports on 192.168.3.65 are closed

All 1000 scanned ports on 192.168.3.66 are closed

All 1000 scanned ports on 192.168.3.67 are closed

All 1000 scanned ports on 192.168.3.68 are closed

All 1000 scanned ports on 192.168.3.69 are closed

All 1000 scanned ports on 192.168.3.71 are closed

All 1000 scanned ports on 192.168.3.72 are closed

All 1000 scanned ports on 192.168.3.73 are closed

All 1000 scanned ports on 192.168.3.74 are closed

All 1000 scanned ports on 192.168.3.76 are closed

All 1000 scanned ports on 192.168.3.77 are closed

All 1000 scanned ports on 192.168.3.78 are closed

All 1000 scanned ports on 192.168.3.79 are closed

All 1000 scanned ports on 192.168.3.81 are closed

All 1000 scanned ports on 192.168.3.82 are closed

All 1000 scanned ports on 192.168.3.84 are closed

All 1000 scanned ports on 192.168.3.85 are closed

All 1000 scanned ports on 192.168.3.104 are closed

All 1000 scanned ports on 192.168.3.105 are closed

All 1000 scanned ports on 192.168.3.109 are closed

All 1000 scanned ports on 192.168.3.110 are closed

All 1000 scanned ports on 192.168.3.123 are closed

All 1000 scanned ports on 192.168.3.124 are closed

All 1000 scanned ports on 192.168.3.147 are closed

All 1000 scanned ports on 192.168.3.148 are closed

All 1000 scanned ports on 192.168.3.151 are closed

All 1000 scanned ports on 192.168.3.152 are closed

All 1000 scanned ports on 192.168.3.153 are closed

All 1000 scanned ports on 192.168.3.154 are closed

All 1000 scanned ports on 192.168.3.156 are closed

All 1000 scanned ports on 192.168.3.157 are closed

All 1000 scanned ports on 192.168.3.165 are closed

All 1000 scanned ports on 192.168.3.166 are closed

All 1000 scanned ports on 192.168.3.170 are closed

All 1000 scanned ports on 192.168.3.171 are closed

All 1000 scanned ports on 192.168.3.176 are closed

All 1000 scanned ports on 192.168.3.177 are closed

All 1000 scanned ports on 192.168.3.178 are closed

All 1000 scanned ports on 192.168.3.179 are closed

All 1000 scanned ports on 192.168.3.180 are closed

All 1000 scanned ports on 192.168.3.181 are closed

All 1000 scanned ports on 192.168.3.182 are closed

All 1000 scanned ports on 192.168.3.183 are closed

All 1000 scanned ports on 192.168.3.184 are closed

All 1000 scanned ports on 192.168.3.185 are closed

All 1000 scanned ports on 192.168.3.186 are closed

All 1000 scanned ports on 192.168.3.187 are closed

All 1000 scanned ports on 192.168.3.188 are closed

All 1000 scanned ports on 192.168.3.189 are closed

All 1000 scanned ports on 192.168.3.190 are closed

All 1000 scanned ports on 192.168.3.191 are closed

All 1000 scanned ports on 192.168.3.192 are closed

All 1000 scanned ports on 192.168.3.193 are closed

All 1000 scanned ports on 192.168.3.194 are closed

All 1000 scanned ports on 192.168.3.195 are closed

All 1000 scanned ports on 192.168.3.196 are closed

All 1000 scanned ports on 192.168.3.197 are closed

All 1000 scanned ports on 192.168.3.198 are closed

All 1000 scanned ports on 192.168.3.199 are closed

All 1000 scanned ports on 192.168.3.200 are closed

All 1000 scanned ports on 192.168.3.201 are closed

All 1000 scanned ports on 192.168.3.202 are closed

All 1000 scanned ports on 192.168.3.203 are closed

All 1000 scanned ports on 192.168.3.204 are closed

All 1000 scanned ports on 192.168.3.205 are closed

All 1000 scanned ports on 192.168.3.206 are closed

All 1000 scanned ports on 192.168.3.207 are closed

All 1000 scanned ports on 192.168.3.208 are closed

All 1000 scanned ports on 192.168.3.209 are closed

All 1000 scanned ports on 192.168.3.210 are closed

All 1000 scanned ports on 192.168.3.211 are closed

All 1000 scanned ports on 192.168.3.212 are closed

All 1000 scanned ports on 192.168.3.213 are closed

All 1000 scanned ports on 192.168.3.214 are closed

All 1000 scanned ports on 192.168.3.215 are closed

All 1000 scanned ports on 192.168.3.216 are closed

All 1000 scanned ports on 192.168.3.217 are closed

All 1000 scanned ports on 192.168.3.218 are closed

All 1000 scanned ports on 192.168.3.219 are closed

All 1000 scanned ports on 192.168.3.221 are closed

All 1000 scanned ports on 192.168.3.222 are closed

All 1000 scanned ports on 192.168.3.223 are closed

All 1000 scanned ports on 192.168.3.224 are closed

All 1000 scanned ports on 192.168.3.226 are closed

All 1000 scanned ports on 192.168.3.227 are closed

All 1000 scanned ports on 192.168.3.229 are closed

All 1000 scanned ports on 192.168.3.230 are closed

All 1000 scanned ports on 192.168.3.232 are closed

All 1000 scanned ports on 192.168.3.233 are closed

All 1000 scanned ports on 192.168.3.234 are closed

All 1000 scanned ports on 192.168.3.235 are closed

All 1000 scanned ports on 192.168.3.246 are closed

All 1000 scanned ports on 192.168.3.247 are closed

Nmap done: 1024 IP addresses (220 hosts up) scanned in 299.54 seconds
lockhart@kitchen ~ $

fasta6
Level 1
Level 1
Posts: 6
Joined: Wed Aug 05, 2009 12:06 pm

Re: connecting to XP network to access printer

Post by fasta6 » Thu Aug 06, 2009 9:27 pm

OK, I tried it using the IP address of the printer's host PC again and it installed the printer and it shows up fine. However, I won't print to it. The status in the print window just shows "processing". And the print queue on the PC with the printer doesn't show any print jobs.

User avatar
GuiH
Level 1
Level 1
Posts: 34
Joined: Fri May 08, 2009 9:26 pm

Re: connecting to XP network to access printer

Post by GuiH » Thu Aug 06, 2009 9:36 pm

I guess the way to share my printer with a fully network based on linux. Have one compatible thread?!
Image
Image
Image
Image

altair4
Level 19
Level 19
Posts: 9751
Joined: Tue Feb 03, 2009 10:27 am

Re: connecting to XP network to access printer

Post by altair4 » Fri Aug 07, 2009 9:06 am

Had I known you had so many machines on your "home network" I would have asked what the ip address is of the WinXP and the Mint machines.

The nmap command only shows one machine with open ports: 192.168.1.103 which based on the smbtree output is the Mint Desktop. If the WinXP machine is part of the other machines on that network it has no open ports which most likely means there is a firewall in place. If I had that many machines on my network I would have a firewall on that box as well.

If I'm right, you're going to have to configure that WinXP firewall to allow printer access to at least 192.168.1.103. I can't help you on that end. If there was a safe way to disable the WinXP firewall and then try to access the printer you would know for sure that the firewall is the problem.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.

fasta6
Level 1
Level 1
Posts: 6
Joined: Wed Aug 05, 2009 12:06 pm

Re: connecting to XP network to access printer

Post by fasta6 » Fri Aug 07, 2009 6:34 pm

I only have 2 machines on my network. One XP machine and the Linux Mint machine.

altair4
Level 19
Level 19
Posts: 9751
Joined: Tue Feb 03, 2009 10:27 am

Re: connecting to XP network to access printer

Post by altair4 » Sat Aug 08, 2009 8:23 am

If your using a wireless modem you might want to check the security settings because according to nmap:
Nmap done: 1024 IP addresses (220 hosts up) scanned in 299.54 seconds
you're providing internet access to the whole town.

In any event, have you turned off the windows firewall ( temporarily ) to see if you can access the windows printer?
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.

fasta6
Level 1
Level 1
Posts: 6
Joined: Wed Aug 05, 2009 12:06 pm

Re: connecting to XP network to access printer

Post by fasta6 » Mon Aug 10, 2009 2:30 pm

I'm using a wired/wireless router, wired for the home PC's and wireless for my laptop. But I'm using MAC address filtering for security, so only my laptop can connect wirelessly.

I can see the windows printer now, and it installed OK, but I can't print to it. I disabled the firewall on the printer's host PC and still no luck. The print queue on the linux machine shows 1 print job in progress, but the windows machine shows nothing in the queue.

Post Reply

Return to “Newbie Questions”