Topic: Successful migration Win2K->SME! (mostly anyway)

[dave]

I finally did it.  I was able to store my data from the Win2K server and reloaded the main server with SME 5.6 and update 4.  I had to redo my Win2K workstations domain settings but so everything is working fine with one exception.  I haven't been able to set up the network printer.

I have an Epson Stylus 440 color printer.  I went to server manager and set up the printer on local port 1 (yes, the printer is connected to LPT1 on the server).  The configuration says all is OK.  I went to a workstation and created a network printer pointing to the this network printer.  I open printer properties on the workstation and I get an access denied message.  I checked the logs and I get messages refering to the port not being available.  This printer was setup with Win2K server as the network printer and worked fine so I know the port and printer works but something in SME is either not recognizing the port or something else is tying up the interrupt or I/O address and SME thinks it's not working.  

Does anyone know of a utility that can show what the state of system interrupts and/or I/O addys are?  Are there any suggestions as to where to start?

If it helps, the system is:
dual PII xeon 450 MB, an older Intel board.
1 GIG RAM
Intel EEPro 100 NIC
Proliant smart 2/DH raid card, 3 internal arrays, one external
Matrox AGP video card
running SME Server 5.6u4 in server only mode
Standard IDE CD ROM drive

I can't think of anything else, let me know if more info is needed.  Any help would be appreciated.

Dave

[Bill Pflaumer]

What is the OS of the workstations? Is the SME a Domain Controller? Is WINS enabled on the SME box? Is the Wins IP in the WKSTATIONS TCP/IP Settings? DID U Create Machine accounts on the SME Box?

I had a problem where a shared printer on an XPPRO caused Access Denied in a NT4 Domain. For some reason the XPPRO was registered on the WINS DB to an IP not existent on the network (using nbtstat at the NT4 box.) It was registered to the IP on the AOL miniport driver on the XP-Pro PC. The point here is, this may be some type of resolution problem.

Bill

[dave]

Thanks for the reply Bill,

The workstations are Windows 2000 Pro and XP Home.  Both have returned the same error.  The SME is set up to be a domain controller.  I don't know if SME is using WINS, I was hoping to be able to not use it, my switch logs a large amount of broadcast traffic that I was attributing to the Windows resource announcements (please correct me if I'm wrong, but I think that's due to WINS broadcasts).  

All my workstations get IP addresses via DHCP with MAC address reservations through the other SME server.  This other box is the firewall/internet gateway with email/web/DHCP/primary DNS services running.  This box has been up and running for the last year and a half or more.

I don't know how to create 'machine accounts' on the SME box, I thought all that was needed was to create the user accounts.  The Win2K domain required machine accounts be set up for each workstation (starting with NT, Win9X machines didn't need an account, just the user ID).  I did set up all the user accounts on the SME box.

As I write this, I recall setting up DHCP to provide a WINS address, but I don't remember if I set that up on the SME box or if it was set up when I had Win2K providing DHCP services.  I'll check that again when I get home (I'm at work right now).

It's possible it's a resolution issue but I would imagine the user shares wouldn't be available if names were not set up properly.  I have no experience with sharing network resources on Linux apart from the user shares created when you create a user ID.

My biggest concern was the log entries stating the lpr service couldn't find a printer port - these logs are on the SME box.  I tried setting up the printer on all 3 available local printer ports. I was initially guessing it was a resource conflict.  I've seen certain software expect the default printer port to be on IRQ 7 only and if PNP allocated the default IRQ to something else, the software would say no ports were available.  This is why I tried all 3 ports, if SME is expecting LPT1 to be on IRQ7, LPT2 to be on 5 and 3 to be on 2/9, I hoped the internal printer port would be recognized as one of these.  I was wrong.

I know the combination works, it worked fine for quite a while under Win2K server.  If I can't figure this out, I won't be going back to 2K or anything, if necessary I can use a network print server or something but I'd prefer to keep the printer on the server.

I will check the WINS settings when I get home, in the mean time does anyone else have any ideas?

Dave

[Walter Padgett]

Good Afternoon,

I didn't know that WinXP Home edition could log into a domain? You might want to read this http://forums.contribs.org/index.php?topic=18287.msg71766#msg71766 as it references what I went through to join XP Pro machines to a SME domain box. There are some other related links in the discussion thread as well that might assist you further. I haven't setup a network printer yet but that's my next project. I have a HP JetDirect printer that looks like it will be very easy to setup in SME. JetDirect's have been very easy to setup on other OS's and I don't anticipate any trouble.

Hope this helps,

Wally

[steve]

what happens if you open your printers folder on the client, open up a window to the server (Start -->Run-->\Servername -->enter key) and drag the printer from the SME server into your printers folder?
it should prompt you to install the drivers and there should be no problems after that. I have a printer on my SME at home and print to it without any problems from XP home, Win2K and Win98SE.

steve

[dave]

Walter:  

I followed your link, sounds like you had some serious head scratching going on there.  There's some more customizations I want to make, I did successfully set up the user shares on a second hard drive.  I have another one in the system that I want to use for a common share that everyone has read/write access to.  I hope you got everything going like you wanted.  Did you ever get SME in server mode to get an IP address by DHCP?  

You're right, XP Home doesn't have the ability to login into a domain, and by default the typical windows login screen doesn't appear, you just click a user name (or picture, I think).  You have to go into control panel and change some settings to force a system login with password.  You're only logging in locally but if the user name and password for the local system is the same as the SME account, when you browse the network you can see network shares and such - at least that's how it works from my Wife's laptop...

Steve:

I haven't tried finding network resources that way, I'll give that a try and post here what I find.

Thanks for the input everyone,

Dave

[Laurence Griffiths]

I had the same problems, but then decided to try to print a test page. - It worked!

I still get "access denied", but the printing works perfectly and that is all I am worried about.

[Shane Wilkens]

Add your login name to the following locations and restart the SMB service:

printer admin = admin

and ditto in the templates directory under 11printerAdmin

You will then NOT get the access denied message.

[Walter Padgett]

Good Evening,

Dave:

No I haven't found anything concerning getting an IP via DHCP in a server-only mode.

Everyone:

Since we're on the subject of printing, is there anyway to setup a SME box to allow just anyone to print to the printers it manages? I would like to setup a SME box to do nothing but manage the printers and print jobs but I don't want to go through the hassle of setting all 1700+ users up on the box.

A penny for your thoughts,

Wally

[Shane Wilkens]

Wally,

I did this:

guest account = public
guest ok = yes
map to guest = bad user

Under [printers] put

guest ok = yes

Ditto to update templates to reflect the above

I have a Mitel 5.1.2 print-server set up for 50 users and printing to 15 printers in 4 location across a WAN

Shane

PS - as per my previous post re: access denied with Windows 2000/XP and NT clients - tacking the user-names onto the printer admin = fixes this

[dave]

Good ideas all.  I'll try them and see if the 'access denied' message goes away, it should based on the suggestions.  These changes should go in the smb.conf file, correct?

I did install the print queue management contrib and I could see the print jobs actually being queued up but it looks like there's something wrong with the printer port.  Well, I don't think there's anything really wrong, I think SME just doesn't like the hardware or something.  The set up worked fine when running Win2K server so I know everything works.  Does anyone have any clues to troubleshooting the lpr (I think that's what it's called) module?

Thanks for everyones input,

Dave