Printable View
I have a Windows 2003 Active Directory Domain setup at home with a few hardwired systems and 2 wireless systems. The problem is that my printer is connected (USB) to the server and shared out and selected to be listed in the Directory but it still cant be seen on the network except for one hardwired system running XP. The others are running 2000/XP and are hardwired or wireless and can not see or access this printer.
Any suggestions?
Are the other machines able to see the server and connect to it?
If not it could either be a DHCP or security issue.
Well one system (wireless) is supposed to be DHCP but it doesnt get an IP from my router running dhcp as the server doesnt run dhcp and this is causing problems logging into the domain. :( XP SP2 system with the firewall off. How can it log on to the domain when the linksys wireless usb controller may not be running until logged into the desktop?
If I log in locally to the wireless one then I can not see the printer. Doesnt it not matter if your logged into the domain or not?
So you only have 1 DHCP server right? Are all the machines getting their IP's from this router or have you manually set any?
When you say 'wireless usb controller' you mean a wireless NIC?
Only the router is assigning IPs. The server is not. The XP SP2 wireless system was manually entered in IP info because the dhcp info was connecting but couldnt assign an IP. So no internet access because of this and surely no visible printer either. The manually entered in info is correct as I get internet access but just no access to log on to the domain.
Can you ping the server? (by Name or IP)
I'll try that in the morning as its getting a little late and have already shut down all but 2 systems.
I dont know what I missed or have misconfigured as I can add workstations to the domain and log on to those hardwired but not those that are wireless.
I think I will also step back a bit and create some background info and network setup for you.
Be back tomorrow.
Thanks so far :)
Yes I know what you mean, I've been up since 5am...
See you tomorrow :)
Seems I have somewhat of a solution, I type in the FQ Path of the printer in the Add Printer "Connect to this printer," Name box it found the printer but not when you try to browser for it. So I was able to add the printer to one of the wireless systems that I logged on to. Doesnt seem like its listed in the AD directory list?
You probably can't browse to it because your in a workgroup, not the domain.
It doesn't list even for the machines in the domain?
The wireless workstation is added to the domain and I can log on using an account (admin too ) and still not see any other computers in the domain, let alone the printer. :(
No workgroup as I am adding them all to the domain.
I just typed the IP address of the server, and was shown the printers. I opened it, and double-clicked on the printer that I wanted installed.
Is your server running WINS? If not you might want to try that.
That does not help me dglienna as that is for your situation and not mine.
Also, I posted that I typed in the fully qualified server name and printer share name and it works.
No, I am not running wins. The printer should show as an active printer under my server in the list when adding a network printer.
I was reading up on Wins, should I be running it on my server then? I'm currently not running it.
*BUMP*
It's a good idea. Even though everything is supposed to run via DNS now, WINS is usually the first thing used for name resolution. Personally I'd move DHCP to the server as well.
Well with the wireless systems it takes a few MINUTES to logon to the domain and if the DHCP was moved to the server it may take even longer?
I'll install WINS then and hopefully its straight forward to install. I'll post back when I do it today.
Installing WINS is pretty simple. Moving DHCP wouldn't effect the time since you don't need to login to the domain to use it. If you moved the DHCP to the server you could add the WINS server IP in so it would be automatic. You could also add the the server as the time server which is also something that could cause you issues.