adding a printer FIX

From: Joe (Joe_at_discussions.microsoft.com)
Date: 11/30/04


Date: Tue, 30 Nov 2004 09:57:02 -0800

Hello,

After aproximately 20 or more posts and 1 weeks time I found a solution!
 
This setup or configuration is not common but very effective in my case.
I do think some smaller networks will benefit.
Setup:
1 server 2003 enterprise machine: IIS, mail and File server- and now partial
print server.

2 internal XP machines
2 external XP machines

The server has two nic cards 1 public IP and the other intenal IP out to an
8 port switch.( no router)
the server is a workstation not a DC so this is what is not normal in this
case.Also a workgroup enviroment and no DHCP

What was the problem?
The internal XP machines could see everthing and connect. The internal
network was just fine all printers shared and accessable.
However, the printers were not on the server itself. They were both
connected to one of the internal XP machines.

Well what seemed to be the problem?

Well... The external XP machines had no problem connecting VPN but could not
"see" the printers. Very strange? I could access, change and delete files on
the shares. However I tried i could not get the external XP machines to
connect even though they were shared. Hmmm...? I couldn't even find them!

Resolution
1. Join all internal machines to the same workgroup as the server.

2. Remote into the server and add the shared printers.This leaves you
without a physical connection to the server and no SCSI cards need be
added.It also gives you the ability to print directly from the server if ever
need.(sometimes it is).

3.You must run the wizard in XP service pack 2 to allow printer and file
sharing and make sure you change the workgroup name to the servers workgroup
while doing so.

4.Remote into the server again and run the new connection wizard select make
an advanced connection and proceed to allow VPN connections.

5. After completeing that go to My connections folder and look for the
remote connection you just made and right-click on it > properties>networking
tab>TCP/IP>properties. Select to give static IP's to the incoming VPN
machines. You can put whatever you want. But I would match my network IP's.
Do not tick the box that says "allow calling computers to select thier own
IP" something to that effect I don't completely remeber. Apply everthing you
have done and back out of there. On the general tab tick the box that
says"Show icon in notification area when connected" also make sure the Allow
Virtual Private connections is ticked just avobe it. Next on the users tab
select the users who are permitted to connect.

6.Also on the networking tab you have to have the checkbox that says "Allow
callers to acces my local area network".

7. Go to the remote machines physically and run the connection wizard and
select to "connect to the network at my workplace". fill in the reqired
information such as the public IP of the server. Once you make that
connection an icon will be put on your desktop. Double click and connect.
After you connect you can see the Icon on your remote machine in the system
tray. Lower right hand side of the windows toolbar. Double click it and look
at the support tab you will see the details and the server IP. It should be
one that you statically configured earlier.

8. We are almost done!! Pheewww. Now click start run and type
\\IP of VPN\sharename
example mine is
\\192.168.254.100\Sharename. However this will work for files but not
printers even if they are shared. you must type
\\192.164.254.100\ this will open up all shared folders and you will now
see printers and faxes folder. Open that folder and right click on the
printer you wand and connect!!! woot!

9. One last thing. If you connect and try to open a share you may be
prompted for you credentials again. If so... enter the ones you need to have
access. If you want to stop this from happening just add your username and
password from the XP machines identically on the server. No logon scripts = )

I will put this in a complete edited form for download on
www.Animocracy.com/downloads by the tonight in a PDF. Please give me sometime.

Hope this helps
Joe



Relevant Pages

  • Re: Adding Printer FIX
    ... > print server. ... > 2 internal XP machines PRO ... > network was just fine all printers shared and accessible. ... > without a physical connection to the server and no SCSI cards need be added. ...
    (microsoft.public.windows.server.networking)
  • Re: Adding Printer FIX
    ... server 2003 enterprise machine: IIS, mail and File server- and now partial ... internal XP machines PRO ... the printers were not on the server itself. ... without a physical connection to the server and no SCSI cards need be added. ...
    (microsoft.public.windows.server.networking)
  • Adding Printer FIX
    ... server 2003 enterprise machine: IIS, mail and File server- and now partial ... internal XP machines PRO ... the printers were not on the server itself. ... without a physical connection to the server and no SCSI cards need be added. ...
    (microsoft.public.windows.server.networking)
  • Re: Problem With Internet Sharing
    ... If you're using 50 machines, you must have a domain setup since a workgroup ... the machines not directly connected to the internet because that can cause ... settings too high on the client computers (but not on the server). ... I also notice the Ethernet Local Area Connection IP address is from APIPA so ...
    (microsoft.public.windowsxp.network_web)
  • Re: Using Remote Terminal session W2003, Spooler Event Log entry
    ... My guess is that you have your terminal server connection settings to ... Resources tab and unchecking the printers box. ... > the spooler service is not running on the server as there is no ...
    (microsoft.public.windows.server.general)