RE: Printing Issue

anonymous_at_discussions.microsoft.com
Date: 05/06/04 

Date: Thu, 6 May 2004 10:30:11 -0700

Yes these are non employees that would have access to only
one app. Opened the two or three ports it needed
originally and then opened another for the printer. After
that it worked fine for the afternoon when I came in the
next morning it no longer worked from outside the network,
but still worked inside. Double checked all traffic at the
firewall and nothing is being denied access. You can see
it create the clients local printer in the event log and
they do get acces to the db, just will not print to our
network printer.
>-----Original Message-----
>If these are employees connecting to the TS, then I'd put
the Terminal Server on the LAN with the resources to which
they need access.
>
>Times when you use a DMZ are when NON employees need
access to one or two singular applications, not your
entire network, so you put the TS in a DMZ and open ports
between the DMZ and the specific internal resources, i.e.
SQL, IIS...
>
>TS How to & FAQ:
>http://www.workthin.com/tshta.htm
>
>Patrick Rouse
>Microsoft MVP - Terminal Server
>http://www.workthin.com
>
>
>
> ----- anonymous@discussions.microsoft.com wrote: ----
-
>
> The vendor for the server/firewall recomended that
> configuration, Paranoia on my part played a roll as
well.
> This is not something we've done before and my IT
skills
> are limited. Learn as you go kind of thing.
> >-----Original Message-----
> >What is your reasoning for putting the terminal
server in
> the DMZ? I'm not saying that there are not times
when
> this is done, I'm just curious what the situation is
that
> requires this.
> >>Patrick Rouse
> >Microsoft MVP - Terminal Server
> >http://www.workthin.com
> >> ----- Lee wrote: -----
> >> We have just installed a Server 2003 machine
as a
> terminal
> > application server. This machine is in our dmz
and
> needs
> > to be able to print to an HP4050tn on the
inside of
> our
> > firewall. I set the printer up on the terminal
> server as a
> > tcp printer and watched the firewall to see
what
> bounced
> > off, opened the ports it wanted and all was
fine for
> a
> > matter of hours. Now terminal clients on the
inside
> of our
> > firewall can still print to the HP printer but
> remote
> > clients cannot. Rechecked traffic at the
firewall
> and
> > talked to our firewall vendor's support and
the
> firewall
> > does not seem to be involved. Any Ideas?
> >>.
> >
>.
>

Relevant Pages

  • Re: Interesting webserver intrusion (apache 1.3.31, mod_ssl 2.8.18, php 4.3.7)
    ... > fairly tight(only allowing 4 ports in), but perhaps I could tighten it ... The host systems firewall rules govern the access to the jailed system. ... What connections does your server need to ... Perhaps there is a 0-day for your ftp server out there. ...
    (Incidents)
  • Re: Unable to join AD domain from DMZ network
    ... To me that points to something outside the machine (Firewall most likely culprit) ... > the captured traffic between the server in DMZ to the DC from internal ... >>> authentication from DMZ to 2003 AD internal network. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Add 2nd NIC after intial install?
    ... My biggest question with 1 NIC is: even if workstations are protected with individual firewall products, what is protecting the SBS server itself if ports are open for remote access through the Linksys firewall? ...
    (microsoft.public.windows.server.sbs)
  • Re: Source Code to Filter out WindowsMessenger POP-UPS
    ... Zone Alarm does NOT support 'server'. ... Very few ports are open, ... >What you are asking for amounts to a firewall. ... I would NOT search for source code to compile ...
    (microsoft.public.inetserver.iis.security)
  • Re: Using Office Outlook with exchange server behind windows firewall
    ... On our network I have windows firewall turned on, on both my small business server and my windows xp workstations. ... Based on an article I read about all the ports that exhange may use I also tried making exceptions for ports ...
    (microsoft.public.windows.server.sbs)
Loading