Windows Server 2003 [user thin client printing issue]

[esip]

---

Problem:
cannot connect to printer attached to a domain computer.

so i need to re-domain the computer to enable to connect the thin client users[windows server 2003]

I Need Help:
how to fix not to re-domain the computer every time i restart the windows server 2003.

Comment:
im doing this everyday re-domain and again and again to enable to connect
is there any problem to my server?
i need suggestions please.
thanks.

[Devian]

can you please clear things up? like...

-is server or domain computer the one with Win2k3?
-what kind of thin client machines do u have?
-is the thin client having connection problem and that your solution is to re-domain the server or the thin client?

please be reminded that in order to connect to a domain resource you must authenticate or login using a valid domain username with access to that resource.

[esip]

can you please clear things up? like...

-is server or domain computer the one with Win2k3?
-what kind of thin client machines do u have?
-is the thin client having connection problem and that your solution is to re-domain the server or the thin client?

please be reminded that in order to connect to a domain resource you must authenticate or login using a valid domain username with access to that resource.

ok i have a domain computer running windows xp and attached to it is a printer.

my problem is everytime the server(Win2k3) is restarted,
the thin client users cannot connect to the domain computer(with printer attached), so i need to re-domain the domain computer(with printer attached) again to enable the thin client users to connect to the domain computer(with printer attached) or to the printer so i can print..

is this a server problem or its just the way it is?
all i want is not to re-domain and re-domain again and again..

[Devian]

ok i have a domain computer running windows xp and attached to it is a printer.

my problem is everytime the server(Win2k3) is restarted,
the thin client users cannot connect to the domain computer(with printer attached), so i need to re-domain the domain computer(with printer attached) again to enable the thin client users to connect to the domain computer(with printer attached) or to the printer so i can print..

is this a server problem or its just the way it is?
all i want is not to re-domain and re-domain again and again..

Ok. I get it.

So this server (win2k3) is your DC and this xp machine (with printer) is a domain member. Is your TC machine a member of the domain too? Can you send me the error message?

[ojisang]

nka deep freeze u bro? namasin lng....

[esip]

nka deep freeze u bro? namasin lng....

Nope im not using any freeze thingy..

[mr.twin]

ask pod ko sa mga expert sa domain server.... gusto ko buhat ug printer server so naa ko 5 units ip printer wla probs pag connect sa domain kay naka IP man , pero if parallel port printer lang so naka connect sa local pc.. unsa mag setup sa parallel printer nga mo connect sya sa print server.... 5 ka ip printer din 5 pod ka parallel port printer connect to local... pero dli ta gamit ug lan press unsa yaha setup...