RE: [WinMac] Remote Access / Appletalk


KR(krushing[at]cecasun.utc.edu)
Fri, 14 May 1999 14:01:56 -0400


WinMac Digest #311 - Friday, May 14, 1999

  Sharing Printers/Files w/win boxes
          by "Matt Montagne" <montagmj@mail.milwaukee.k12.wi.us>
  Remote Access / Appletalk
          by "Jason Clement" <Jason@GiSCO.net>
  R: [WinMac] Sharing Printers/Files w/win boxes
          by "Alessio Giombini" <a.giombini@lasernet.it>
  RE: [WinMac] Remote Access / Appletalk
          by "Hetzel, Thomas" <TLHetzel@metatec.com>
  Re: [WinMac] Sharing Printers/Files w/win boxes
          by "Curtis Wilcox" <cwcx@uhura.cc.rochester.edu>
  JetDirect names change: Mac printing
          by "Parker, Douglas" <douglas.parker@lmco.com>
  Printer management
          by "Daniel L. Schwartz" <expresso@snip.net>
  Re: [WinMac] Remote Access / Appletalk
          by "Bruce Johnson" <johnson@Pharmacy.Arizona.EDU>
  Re: [WinMac] Remote Access / Appletalk
          by "Darron Spohn" <dspohn@clicknet.com>
  RE: [WinMac] JetDirect names change: Mac printing
          by <PetersJB@nswccd.navy.mil>
  Re: [WinMac] JetDirect names change: Mac printing
          by "Curtis Wilcox" <cwcx@uhura.cc.rochester.edu>
  RE: [WinMac] Remote Access / Appletalk
          by "KR" <krushing@cecasun.utc.edu>

Subject: Sharing Printers/Files w/win boxes
From: Matt Montagne <montagmj@mail.milwaukee.k12.wi.us>
Date: Thu, 13 May 1999 22:20:42 -0500
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

I am trying to create small network of computers at the elementary school I
work at. Each workgroup has six HP Vectra VL computers (running Win '95)
with factory installed 10/100 Mb 3COM Fast Etherlink XL Network Interface
Cards. They are all linked together with an Ansante Friendly Net 8 Port
Hub. I would like them to be able to share one of the computer's HP
Deskjet Printers (it is not an ethernet printer.) I enabled file sharing
at all stations and I enabled print sharing at the station that is attached
to the printer. Each station has a unique network identity and they are
all a part of the same workgroup. The primary Netork Logon is Client for
Microsoft Networks and NetBUEI is installed and running. The Device
Manager shows that the computer recognizes the NIC. Also, all activity
LED's on the hub and on the boxes are green. With all of this said, each
time I go to Network Neighborhood and I try to browse the Entire Network I
receive a message saying, "Unable to Browse the Network. The Network is
not accessible." I am very comfortable placing a Mac on a network and I
don't know why this is so difficult. Do I have to create a password that
users use when the boxes are booted up? Right now I just click "Cancel" in
the Network Password Dialogue box after the boxes boot up. What am I
forgetting to do here?

Thanks for your help.
Matt Montagne
Computer Specialist
38th Street School
Milwaukee Public Schools

Subject: Remote Access / Appletalk
From: "Jason Clement" <Jason@GiSCO.net>
Date: Thu, 13 May 1999 22:20:44 -0500
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

I have a question I am hoping someone can help out with. I am one of about
20 Macs on an NT network. I have tried to access my workstation at the
office from home using Remote Access several times unsuccessfully. The
System Administrator refuses to install Appletalk because of "security
reasons" and I was wondering if anyone knows if this could be the problem.

Thanks for any and all info.

--
Jason Clement
12291 County Rte 5
Chaumont, NY 13622

315.686.4655 315.771.0911 (cell) Jason@GiSCO.net

Subject: R: [WinMac] Sharing Printers/Files w/win boxes From: "Alessio Giombini" <a.giombini@lasernet.it> Date: Fri, 14 May 1999 08:52:44 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed"

did u also share the printer (not only print sharing)?

----- Original Message ----- From: Matt Montagne <montagmj@mail.milwaukee.k12.wi.us> To: The Windows-MacOS cooperation list <winmac@xerxes.frit.utexas.edu> Sent: Friday, May 14, 1999 5:20 AM Subject: [WinMac] Sharing Printers/Files w/win boxes

> I am trying to create small network of computers at the elementary school I > work at. Each workgroup has six HP Vectra VL computers (running Win '95) > with factory installed 10/100 Mb 3COM Fast Etherlink XL Network Interface > Cards. They are all linked together with an Ansante Friendly Net 8 Port > Hub. I would like them to be able to share one of the computer's HP > Deskjet Printers (it is not an ethernet printer.) I enabled file sharing > at all stations and I enabled print sharing at the station that is attached > to the printer. [snip] With all of this said, each > time I go to Network Neighborhood and I try to browse the Entire Network I > receive a message saying, "Unable to Browse the Network. The Network is > not accessible."

Subject: RE: [WinMac] Remote Access / Appletalk From: "Hetzel, Thomas" <TLHetzel@metatec.com> Date: Fri, 14 May 1999 08:53:30 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed"

Timbuktu would allow you to access your computer from home without using Appletalk. Timbuktu could use TCP/IP to access files or control your computer as well as a few other features.

> ---------- > From: Jason Clement > Reply To: The Windows-MacOS cooperation list > Sent: Thursday, May 13, 1999 11:20 PM > To: The Windows-MacOS cooperation list > Subject: [WinMac] Remote Access / Appletalk > > I have a question I am hoping someone can help out with. I am one of about > 20 Macs on an NT network. I have tried to access my workstation at the > office from home using Remote Access several times unsuccessfully. The > System Administrator refuses to install Appletalk because of "security > reasons" and I was wondering if anyone knows if this could be the problem. > > Thanks for any and all info. >

Subject: Re: [WinMac] Sharing Printers/Files w/win boxes From: Curtis Wilcox <cwcx@uhura.cc.rochester.edu> Date: Fri, 14 May 1999 08:53:33 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed"

At 10:20 PM 5/13/99 -0500, Matt Montagne wrote:

>LED's on the hub and on the boxes are green. With all of this said, each >time I go to Network Neighborhood and I try to browse the Entire Network I >receive a message saying, "Unable to Browse the Network. The Network is >not accessible." I am very comfortable placing a Mac on a network and I >don't know why this is so difficult. Do I have to create a password that >users use when the boxes are booted up? Right now I just click "Cancel" in >the Network Password Dialogue box after the boxes boot up. What am I >forgetting to do here?

Yep, you have to type *something* in for the username and password at boot else you can't browse the network. If that's a nuisance you can download TweakUI from Microsoft (or other download sources) and use that control panel's auto-logon setting.

BTW, you only have to run File and printer sharing on the machine that is doing the sharing.

-- 
Curtis Wilcox          cwcx@ats.rochester.edu
Desktop Systems Consultant       716/274-1160
Eastman School of Music       Pager: x12-3290

Subject: JetDirect names change: Mac printing From: "Parker, Douglas" <douglas.parker@lmco.com> Date: Fri, 14 May 1999 08:53:36 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed"

I've read the FAQ--this isn't in it.

I have a mix of Macs and WIN95/NT systems in an environment with NT servers. Printers are connected to HP JetDirects. WIN systems print through the NT print server to the printers--no problems there. Our Macs had been printing through NT also, but that's been disabled--now the Macs print directly to the printer via AppleTalk through the JetDirects.

But we're having big problems with the naming of the JetDirects: If the NT queue is called ABC, and if the JetDirect is named ABC (SFM is not enabled on the NT print server--I'm pretty sure that's right--the Mac output goes directly to the JetDirect and never touches the NT queue), then after a period of time (weeks) the JetDirect renames itself to either one of two things:

1) ABC1 or 2) HP LaserJet Series n

where n is some integer. The value for n never stays consistent from printer to printer. It's obviously picking up the next integer available as it resets its name on the fly, or as you power cycle the printer.

We need to pin down a permanent name for our printers so our Macs can print.

Thoughts or insights? Thanks ahead of time.

Doug

Subject: Printer management From: "Daniel L. Schwartz" <expresso@snip.net> Date: Fri, 14 May 1999 09:01:25 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed"

The following crossed my desk.

Cheers! Dan

DISCLAIMER: I HAVE NO FINANCIAL INTEREST IN EITHER OUTFIT... > > 1) PRINT QUEUE MANAGER: HIGH POWER PRINT CONTOL > ----------------------------------------------- > [snip]

The product claims:

>It is the only tool in existence that allows you to manually Drag >and Drop or automatically re-direct print jobs to other printers or >queues, Broadcast Print, Load Balance, Printer Disaster Recovery, >Move, Copy, Delete, or Pause Print Jobs, and much more from a central >console among networked printers in an NT enterprise environment.

See: >Print Queue Manager is available now in a fully functional 30-day trial >version at http://www.sunbelt-software.com/pqm.htm >It is priced at only $995.00 for an NT Print Server, with volume and >academic discounts available and immediate delivery.

-----------------------------------------------------------------

<mailto:expresso@snip.net>

-----------------------------------------------------------------

Subject: Re: [WinMac] Remote Access / Appletalk From: Bruce Johnson <johnson@Pharmacy.Arizona.EDU> Date: Fri, 14 May 1999 10:18:12 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed"

Hmmmm..."Won't run AppleTalk for _security_ reasons"...that's a new one by me. Exactly _how_ is AppleTalk a security problem?

Yep, that might be the problem, if you're going through an NT remote access server. Out of the box, with the proprietary MS authentication scheme only Windows systems can connect, iirc.

They have to go to the standard PAPS/CHAPS (I forget the exact one or it may be both) authentication. And then they would have to run Services for Macintosh so you could talk to the desktop box.

Of course, if they did that, why you could save your files on the file server where they're reasonably safe and backed up regularly instead of the desktop boxes where vital corporate data is at the whim of individual workers doing backups.

These are exactly the kind of roadblocks that cause people to do things like install modems on their desktop machines so they can dial in to get their work done. Thus creating _real_ security problems.

<sigh>

/mini-rant

Am I the only sysadmin on the planet who thinks his job is to make life _easier_ for the users rather than _harder_?

/mini-rant

Jason Clement wrote: > > I have a question I am hoping someone can help out with. I am one of about > 20 Macs on an NT network. I have tried to access my workstation at the > office from home using Remote Access several times unsuccessfully. The > System Administrator refuses to install Appletalk because of "security > reasons" and I was wondering if anyone knows if this could be the problem.

Subject: Re: [WinMac] Remote Access / Appletalk From: "Darron Spohn" <dspohn@clicknet.com> Date: Fri, 14 May 1999 08:55:28 -0700 Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit

> /mini-rant > > Am I the only sysadmin on the planet who thinks his job is to make life > _easier_ for the users rather than _harder_? > > /mini-rant

Everyone in my department thinks you must be. Are you looking for a job?

--
Darron Spohn
Publications Manager
ClickNet Software Corporation
http://www.clicknet.com

Subject: RE: [WinMac] JetDirect names change: Mac printing From: PetersJB@nswccd.navy.mil Date: Fri, 14 May 1999 12:17:27 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252"

Doug,

Under similar conditions, I've used two techniques to address the problems you've outlined: First, if your network has been configured with multiple AppleTalk zones, assign the printer (or print queue) to an appropriate zone. This avoids clustering so many printers into the default zone. Second, I try to give a printer similar but not identical names for it's various identities.

For instance, the out-of-the-box default name for an LJ 4000 using the AppleTalk protocol might be "HP LaserJet 4000 Series". As you've seen, as each similar printer is brought on-line subsequently, the "1", "2", etc. is appended to make the network identity of any printer in a zone be unique. If I rename the printer (via LaserJet Utility) to "LJ 4000, Code 5500", then if the printer is offered through a print queue I might name it "LJ 4000, Code 5500 (Q)". Similar names are given to appearances under NetWare or when using HPs network printing apparatus.

We have dozens of printers on our network and I see 15 generically named LaserJet 4000 printers in the Chooser. I can't imagine trying to identify the one I want. The half-dozen I've renamed and re-zoned are easy to find and use along with their NT print queue counterparts.

Hope this helps. ________________________________________________________________________ Brooks Peters (301) 227-1243 (voice) NSWC - Carderock Division (301) 227-5930 (fax) Code 5500 (Bldg. 18, Rm. 127) mailto:PetersJB@nswccd.navy.mil 9500 MacArthur Blvd. West Bethesda, MD 20817-5700

> ---------- > From: Parker, Douglas > Sent: Friday, May 14, 1999 9:53 AM > Subject: [WinMac] JetDirect names change: Mac printing > > I've read the FAQ--this isn't in it. > > I have a mix of Macs and WIN95/NT systems in an environment with NT > servers. > Printers are connected to HP JetDirects. WIN systems print through the NT > print server to the printers--no problems there. Our Macs had been > printing > through NT also, but that's been disabled--now the Macs print directly to > the printer via AppleTalk through the JetDirects. > > But we're having big problems with the naming of the JetDirects: If the NT > queue is called ABC, and if the JetDirect is named ABC (SFM is not enabled > on the NT print server--I'm pretty sure that's right--the Mac output goes > directly to the JetDirect and never touches the NT queue), then after a > period of time (weeks) the JetDirect renames itself to either one of two > things: > > 1) ABC1 > or > 2) HP LaserJet Series n > > where n is some integer. The value for n never stays consistent from > printer > to printer. It's obviously picking up the next integer available as it > resets its name on the fly, or as you power cycle the printer. > > We need to pin down a permanent name for our printers so our Macs can > print.

Subject: Re: [WinMac] JetDirect names change: Mac printing From: Curtis Wilcox <cwcx@uhura.cc.rochester.edu> Date: Fri, 14 May 1999 12:40:57 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"

How is the JetDirect getting its AppleTalk name? Are you using the Apple Printer Utility? If not, that may be all you need to do, use that program to set the name.

At 08:53 AM 5/14/99 -0500, Parker, Douglas wrote: >I've read the FAQ--this isn't in it. > >I have a mix of Macs and WIN95/NT systems in an environment with NT servers. >Printers are connected to HP JetDirects. WIN systems print through the NT >print server to the printers--no problems there. Our Macs had been printing >through NT also, but that's been disabled--now the Macs print directly to >the printer via AppleTalk through the JetDirects. > >But we're having big problems with the naming of the JetDirects: If the NT >queue is called ABC, and if the JetDirect is named ABC (SFM is not enabled >on the NT print server--I'm pretty sure that's right--the Mac output goes >directly to the JetDirect and never touches the NT queue), then after a >period of time (weeks) the JetDirect renames itself to either one of two >things: > > 1) ABC1 >or > 2) HP LaserJet Series n > >where n is some integer. The value for n never stays consistent from printer >to printer. It's obviously picking up the next integer available as it >resets its name on the fly, or as you power cycle the printer. > >We need to pin down a permanent name for our printers so our Macs can print.

-- 
Curtis Wilcox          cwcx@ats.rochester.edu
Desktop Systems Consultant       716/274-1160
Eastman School of Music       Pager: x12-3290

Subject: RE: [WinMac] Remote Access / Appletalk From: KR <krushing@cecasun.utc.edu> Date: Fri, 14 May 1999 14:01:56 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"

>Timbuktu would allow you to access your computer from home without using >Appletalk. Timbuktu could use TCP/IP to access files or control your >computer as well as a few other features. >

Timbuktu is a great piece of software for those of us who need to access remote computers -- either by AppleTalk or by ethernet...

...and another option if your server is permanently affixed to the ethernet is the AppleShare IP 6.1 fileserver software... through the AppleShare IP 6.1 one may access the file server by web browser... or through the chooser... it is a very workable solution for those of us serving both mac and pc clients...

--k

----------------------------------------- Dr. Kittrell Rushing Head, Department of Communication 311 Frist Hall 615 McCallie Avenue University of Tennessee at Chattanooga Chattanooga, TN 37403-2598 Voice: (423) 755-4400 Facsimilie: (423) 755-4695 krushing@cecasun.utc.edu *** http://www.utc.edu/commdept -----------------------------------------

* Windows-MacOS Cooperation List *



This archive was generated by hypermail 2.0b2 on Fri May 14 1999 - 17:07:59 PDT