 |
Hi Guys and gals,
I have a new work laptop that I bring home. I can access my home wireless network to use the internet but I can't see the printer on the base station (home desktop that is always on).
- the printer on the desktop is indeed shared
- the computers are in different workgroups (laptop usually is on work domain but I log in using cached credentials)
Can I use that printer if they are on diff workgroups?
The base station that you are referring to is this the WiFi router and is the printer attached by USB to it ?
What model is it?
If so I have a similar setup using a USR WiFi router.
Basically you have to make sure that the print driver is on each machine that you want to use the printer on.
You can do one of two things to get around the problem quickly:
a) change your home network to a workgroup that matches that of your work.
b) Setup your home computer to run printing services and then on your work laptop setup a TCP/IP printer and point it at the IP of your home computer.
Hope this helps Need.
Casey
This may help, OK its for my USR9108, but the setup should be similar.
Nuts I just reread your question and had a serious D'oH moment.
Ignore all my Router stuff as it doesn't apply.
OK have you tried mapping the printer by IP address ?
\\192.168.x.x\printer
You'll still need the correct print driver on your laptop
Should I set up my home computer to have a static IP in order to use that option?
I don't think I can change my home desktop Workgroup to match the laptop since the laptop is set for our department domain - please correct me if I'm wrong here.
Ben: I'm using a Comtrend DSL modem going into a Microsoft wireless router (got it real cheap of course, they stopped making them)
YES, will make things a hell of a lot easierQuote:
Originally Posted by NeedKarma
WoW interesting how America likes to go for separate bits where as UK prefers all in one gateways.Quote:
Originally Posted by NeedKarma
Ok, I'll set it up in a while, got to open a wine bottle first. :)
BTW - Canada here. We're a little funny about that. Kind of like kiwis and aussies.
Sorry I meant the North Americas
I hear you same as England not being the same as Europe. ;)
I'm about 90% sure (I don't have a laptop to try this anymore as I have switched to Macs). I used to have a WinXP laptop that was part of the domain at work (I'm 90% sure it was). And I had a similar problem where I wanted to print and use shared drives at home. So what I did was setup my home workgroup to be the same as that of work. Then my laptop not being able to find a DC would login me using cached credentials. Once I'm logged in since I had a local work group that trusted anyone in the same workgroup would allow the laptop to use local resources. Accessing the laptop from the local computers was another matter as the laptop did not trust it. I had to share and allow anyone access on the laptop before I would be able to access laptop shares from the local home net.Quote:
Originally Posted by NeedKarma
Casey
P.S. Agree with Ben that static will make things easier.
I agree with Casey on this, just name your workgroup the same name as the domain you use at work. Also I would create the same user account on the other machines on the workgroup with the same password. Authentication should work then, also once you can authenticate on the home workgroup, you shouldn't need static ip addresses (only if you're going to connect via ip address rather than host name)
I just found this whilst browsing around:
http://www.mayabase.nl/index.php?PageID=22
Haven't tried it but maybe worth a look?
Ok, here's the update:
I tried IP printing after setting a static IP on the desktop that has the printer attached. I installed the printer drivers on the laptop as well but the printing gives an error - it just stays in the queue untils it times out.
I'd like to try to workgroup idea but here's my problem: the laptop is set to a domain (xxxx.ca) that I do not want to change since I have to log in at work every once in a while. The desktop is set to MSHOME workgroup. My question is: can I set my desktop to join a non-existent xxxx.ca domain? If I were to set it up like that would I now have a working pivate network (ie. Share folders, printers, etc.)?
Stu - while the IT folk have given me added permissions and rights I don't think I can swing that sweet little utility but it's good to know it's out there, thanks.
Your desktop doesn't need to join the domain at all. It's just a fix, rename your workgroup to xxxx (without the .ca) and leave as a workgroup. As Casey said, the workgroup will then authenticate you cause your laptop (although on a domain) shows the same name when authenticating i.e xxxx\username whether xxxx is a domain or a workgroup. It is different if you wanted to access another domain though, that wouldn't work.
Just rename your workgroup to the same and give it a try, you should then be able to share folders and printers etc from the desktop to the laptop. :)
Try adding the printer as a local printer. When prompted to select the port, add a new TCP/IP port with the IP of the base PC.
No luck boys, I think it may have to do with my restricted permissions. Is it possible that the port used by the printing on the laptop is blocked?
Laptop printing is set to IP_192.168.2.5 and I see it's using port 9100. The desktop is indeed 192.168.2.5, the printer is shared, and I turned off ZoneAlarm on the desktop (in case it was blocking the port). I installed the printer drivers on the laptop.
I still get the "Document failed to print"
Need,
There are two methods for sharing a printer via a PC. One is by using the traditional shared resource method (i.e. shared drive or printer) whereby you are in essence relying on NETBOIS. The other is by using standard TCP/IP.
So when you try to print to a shared printer such as \\desktopcomputer\printername then you are using NETBIOS. First you send your request to the computer in question which then receives your request over NETBIOS and then processes the job locally to the attached printer. However, when you print to a TCP/IP printer you will be sending your request over TCP/IP using port 9100.
Now, your desktop already runs NETBIOS and other than sharing the printer there isn't much you need to do. However, to print to a TCP/IP printer you need to have a server that will listen on the desktop usiong an LPD/LPR service which will then communicate with the printer directly.
You can follow this link which should help you install the service using the add/remote programs method: http://www.le.ac.uk/cc/dsss/docs/print-lpr.shtml
Having said all of that... can you summarize so far what you've done? There's been lots of things you've changed and it would help us narrow the problem down. I'm convinced that you still can print using the printer as a shared resource and using NETBIOS. It could be a simple error somewhere that's preventing you from printing. So what are these settings:
- DOMAIN or WORKGROUP settings on each device
- exact name used in the settings and whether or not domain/workgroup.
- Static/DHCP settings of each device
- For static devices (list all the settings under the network properties. I'm specifically interested in the settings for NETBIOS over TCP/IP options)
- How each device is connected (wired/wireless/esp)
- Usernames used on each (you can protect the innocent here)
Casey
- How the current printer is shared on the desktop (i.e. security permissions)
| All times are GMT -7. The time now is 04:01 AM. |