Re: Adding Printer FIX
From: Joe (Joe_at_discussions.microsoft.com)
Date: 12/01/04
- Next message: Lanwench [MVP - Exchange]: "Re: WINS server"
- Previous message: Bill Grant: "Re: Windows 2003 and subsequent Home Network issues"
- In reply to: Mark-Allen Perry: "Re: Adding Printer FIX"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 30 Nov 2004 17:59:02 -0800
Thanks,
I still have a few bugs to work out at this time but you can get to the
printer and add it. I am having trouble printing at this time but I am sure I
can get it. I had to wait for another PC to arrive today and I just got back
from setting it up. Probably
in a day or so I should have it posted on my site for download as PDF. Sorry
for the delay = )
NAT and RRAS drove me nuts in a small enviroment. and I still may have to
use Ha ha !!
Joe
"Mark-Allen Perry" wrote:
> Very cool. Thanks for posting, Joe.
>
> --
>
> Always try the MS KB first before posting.
> MS KB: http://support.microsoft.com/default.aspx?scid=fh;EN-US;KBHOWTO
> And the answer could have already been posted, so try searching this and other newsgroups first.
> ----
> Mark-Allen Perry
> ALPHA Systems
> Marly, Switzerland
> mark-allen_AT_mvps_DOT_org
>
> "Joe" <Joe@discussions.microsoft.com> wrote in message news:611D5C06-0705-45BC-8D1F-08619F5D543C@microsoft.com...
> Hello,
>
> After approximately 20 or more posts and 1 week’s 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 PRO
> 2 external XP machines PRO
>
> The server has two nic cards 1 public IP and the other internal 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 environment and no DHCP
>
> What was the problem?
> The internal XP machines could see everything and connect. The internal
> network was just fine all printers shared and accessible.
> 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 completing that go to 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 their own
> IP" something to that effect I don't completely remember. Apply everything
> 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 above 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 access 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 required
> 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 Details 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 want and connect!!! woot!
>
> 9. One last thing. If you connect and try to open a share you may be
> prompted for your 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 = )
>
>
> Thank you
> Joseph F. Voldeck II
>
- Next message: Lanwench [MVP - Exchange]: "Re: WINS server"
- Previous message: Bill Grant: "Re: Windows 2003 and subsequent Home Network issues"
- In reply to: Mark-Allen Perry: "Re: Adding Printer FIX"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
