July 24, 2008 01:47am pdt

1. and235100 2,500
2. jss1199 2,000
2. matrixnz 2,000
2. 2PiFL 2,000
5. flubbster 1,600
6. andyalder 1,500
7. SteveH_UK 1,200
8. canali 1,000
8. weellio 1,000
10. KCTS 800
11. thomasja... 500
11. lamaslany 500
13. briancassin 375
14. orangutang 200
14. arekkusu82 200

1. Huntress58 5,800
2. billogle 4,650
3. TimCatur... 3,190
4. tabit 2,600
5. and235100 2,500
6. magigraf 2,450
7. avi_shava 2,400
8. johnt 2,370
9. jss1199 2,000
9. 2PiFL 2,000
9. MASQUERAID 2,000
9. What90 2,000
9. matrixnz 2,000
9. carchitect 2,000
15. KCTS 1,800

04.15.1997 at 02:54PM PDT, ID: 10008027

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

5.0

Changing DOMAIN to Workgroup Logon in WFW

Zone: Windows 3.x Setup

Tags: domain, workgroup, windows, changing

I have a Toshiba laptop on loan that was configured with Windows for Workgroups to logon to an NT Server DOMAIN. While I am using it in my "lab", I'd like to be able to connect to my WORKGROUP and share files. No matter what I've tried, the Toshiba insists on attempting to do a DOMAIN logon instead of WORKGROUP logon. I have an IBM laptop which IS configured for WORKGROUP logon and I have gone as far as to copy the [network] SYSTEM.INI file section from the IBM to the Toshiba but that does not seem to work. In addition, after each boot on the Toshiba, the lines FileSharingLock=Yes and PrintSharingLock=Yes are added to the [network] section. What is causing this and how do I switch from a DOMAIN logon to a WORKGROUP logon (and then back again when needed)? Thanks.

Start your free trial to view this solution

Question Stats

Zone: OS

Question Asked By: gprichar

Solution Provided By: nylja

Participating Experts: 4

Solution Grade: C

Translate:

Loading Advertisement...

Microsoft

Internet Protocols
Applications

Development
OS

Hardware
Windows Security

Apple

Operating Systems
Hardware

Programming
Networking

Software

Internet

Search Engines
File Sharing
WebTrends / Stats
Spy / Ad Blockers

Web Browsers
New Net Users
Web Development
Chat / IM

Anti Spam
Web Servers
Anti-Virus
Email Clients

Gamers

Tips
Online / MMORPG
Puzzle
Emulators

Action / Adventure
Role Playing
Consoles
Game Programming

Strategy
Sports
Misc
Computer Games

Digital Living

Hardware
Automotive
New Net Users
New Users

Software
Digital Music
Gaming World
Home Security

Apple
Networking Hardware

Virus & Spyware

Vulnerabilities
IDS
Encryption
Anti-Virus

Operating Systems Security
Software Firewalls
WebApplications
Cell Phones

Operating Systems
Internet
Hardware Firewalls

Hardware

Displays / Monitors
Handhelds / PDAs
Components
Peripherals
Laptops/Notebooks

Servers
Misc
Apple
Embedded Hardware
Networking Hardware

Storage
Desktops
New Users

Software

System Utilities
Industry Specific
Network Management
Photos / Graphics
Page Layout
VMware
Misc
Web Development

OS
CYGWIN
Voice Recognition
Virtualization
Message Queue
Quality Assurance
Security
Firewalls

MultiMedia Applications
Development
Database
Office / Productivity
Business Management
OS/2 Apps
Server Software
Internet / Email

ITPro

OS
Storage
Encryption
Operating Systems Security
Apple Hardware
Laptops & Notebooks
Servers
Networking Hardware
Peripherals
Devices

Displays / Monitors
WebTrends / Stats
Search Engines
Firewalls
Web Computing
WebApplications
IDS
Vulnerabilities
Email Clients
File Sharing

Spy / Ad Blockers
Web Browsers
Web Servers
Networking
Anti-Virus
Consulting
Chat / IM
Anti Spam

Developer

Web Servers
Web Browsers
Game Programming
Dev Tools
Industry Specific
Office / Productivity

Database
CYGWIN
Web Development
Search Engines
File Sharing
WebTrends / Stats

Programming
Content Management
Application Servers
Protocols

Storage

Removable Backup Media
Storage Technology
Servers

Grid
Remote Access
Backup / Restore

Misc
Hard Drives

Miscellaneous
Security
Development
Linux
VMware

MainFrame OS
Unix
Apple
OS / 2
AS / 400

BeOS
Microsoft
VMS / OpenVMS

Database

Oracle
Miscellaneous
MySQL
Software
Sybase
Contact Management
PostgreSQL
Data Manipulation
Clarion
InterSystems Cache

Siebel
MUMPS
OLAP
SQLBase
SAS
GIS & GPS
4GL
Berkeley DB
DB2
Informix

Interbase / Firebird
FoxPro
Reporting
LDAP
Filemaker Pro
MS SQL Server
dBase
MS Access

Security

Misc
Web Browsers
Software Firewalls
Operating Systems Security
File Sharing

Spy / Ad Blockers
Vulnerabilities
WebApplications
IDS
Anti-Virus

Encryption
Anti Spam
Email Clients
VPN
Chat / IM

Programming

Editors IDEs
Installation
Handhelds / PDAs
Multimedia Programming
System / Kernel
Automation

Algorithms
Game
Signal Processing
Project Management
Open Source
Database

Misc
Languages
Processor Platforms
Theory

Web Development

Scripting
Blogs
Web Servers
Software
Search Engines
Web Graphics
Web Services

Images
Internet Marketing
Images and Photos
Components
Document Imaging
Web Languages/Standards
Illustration

WebApplications
Fonts
WebTrends / Stats
Authoring
Digital Camera Software
Miscellaneous

Networking

Protocols
Apple Networking
Network Management
Message Queue
Application Servers
Content Management
File Servers
Email Servers
Misc
Java Editors & IDEs

Wireless
Networking Hardware
Backup / Restore
System Utilities
ISPs & Hosting
Web Servers
Storage Technology
Removable Backup Media
Servers
Web Computing

Broadband
Grid
OS / 2
Novell Netware
Unix Networking
Windows Networking
Security
Telecommunications
Operating Systems
Linux Networking

Other

Lounge
Business Travel
Community Support
New Net Users

Philosophy / Religion
Math / Science
Miscellaneous
URLs

Expert Lounge
Politics
Puzzles / Riddles
Automotive

Community Support

Suggestions
New to EE
New Topics
CleanUp

Announcements
General
Feedback

Input
EE Bugs

04.17.1997 at 07:09AM PDT, ID: 1775243

TimCaturaHouser:

system.ini is only half the battle.

You also need to look at protocol.ini

I would copy my existing (working system.ini and protocol.ini
to backup files (I usually call them .NIN)

Clean up your system.ini, and no protocol.ini

go to the network icon, and make your workgroup.
copy these new .ini to something like .HOM or .LAB

1 fancy batch file or 2 simple ones to copy the needed system and protocol ini to the apporpate location will make your windows happy.

04.17.1997 at 10:06AM PDT, ID: 1775244

gprichar:

Thanks for trying, Tim, but your answer didn't help at all. What does PROTOCOL.INI have to do with Windows requester-type settings anyway? It only holds the NIC and transport protocols which would stay the same for both DOMAIN and WORKGROUP access. I did as you suggested and wound up back where I started. I need to know what SPECIFIC INI entries or installation/configuration actions control whether DOMAIN or WORKGROUP logon is active.

04.21.1997 at 05:12AM PDT, ID: 1775245

stevebrammer:

In Windows go to the network control panel and set the name of the workgroup to be whatever you want, then in the Startup Options section click the startup button.

In the Startup Settings in the section headed 'Options for Enterprise Networking' uncheck the 'Log on to Windows NT or LAN Manager Domain' option.

Close down the control panel by clicking on the OK buttons that appear, this should update all the necessary system files like system.ini etc. Now restart windows and everything should be OK.

If it still doesn't work it may be because you are logging onto your workgroup with the same username that was used to log on to the Domain. If this is the case delete the 'username.pwl' file for the user concerned as this may hold references to the domain that windows is trying to reference when you log in. This file lives in the \windows directory. Now restart windows and log in again. A new pwl file will be created for the user, but without any references to the domain.

When you want to log in to the Domain again go back to the network control panel as described above and recheck the 'Log on to Windows NT or LAN Manager Domain' option.

04.21.1997 at 10:01AM PDT, ID: 1775246

gprichar:

Thanks for your answer, Steve, but again, it didn't help. Your suggestion is to do the obvious and was the very first thing I tried. The "Domain" logon option is NOT checked and I deleted all .PWL files in the Windows directory but the Domain logon window always pop up when restarting Windows and I cannot logon to my workgroup. ALso no one has yet addressed the mysterious addition of the PrintSharingLock=Yes and FileSharingLock=Yes lines to the SYSTEM.INI file. Something else is going on here. There's some sort of a config "lock" in place and I can't find what it is.

04.28.1997 at 07:07PM PDT, ID: 1775247

tjbynum:

As long as you have File and Print sharing enabled, the FileSharingLock and PrintSharingLock =Yes will continue to come back. This is done via VSHARE.386
Hope that sheds some light on that issue anyhow.

Tim

04.28.1997 at 07:45PM PDT, ID: 1775248

tjbynum:

Ok, I'll give this one a shot.....You've asked specifically what needs to be edited from the SYSTEM.INI file to keep from logging into the WinNT Doamin. You will find the following entries of interest:
LMLogon= (set 1 to log onto LAN Mgr or NT Domain, or 0 to not.)
LogonDomain= this is for the domain name. Remove it if you do not want to log onto the NT.
LogonValidated= try setting this to no as well.

Try changing these prior to loading WFWG. Then del *.pwl Also remove your username from the username=
If this doesn't solve your problem then look around for a win.bat file. If it wasn't your laptop to begin with, then someone may have set it up to run something prior to WIN.COM, which is not uncommon in some people's way of thinking, but a horrifying experience to those in the dark about it. I'm winging this and have not looked up any facts supporting the suggestions, but that *should* offer you the solution that you're looking for, at least at face value.

Let me know how it turns out for you.

Tim

04.29.1997 at 10:36AM PDT, ID: 1775249

gprichar:

Still no soap. This is spooky - there's no WIN.BAT (good suggestion, I shoulda thought of it) on the system. I even searched for hidden files. The system still attempts to do a DOMAIN logon even after I remove all the SYSTEM.INI entries you referred to. And what the heck causes the *SharingLock=Yes statements to me generated??? If it was MY system, I'd be reinstalling WFW about now but that's not an option since I have to return it soon.

05.02.1997 at 01:39PM PDT, ID: 1775250

nylja:

Run admincfg.exe and uncheck forced domain login, if you don't have it expand it from any wfw311 distributionset. It might be passwordprotected an in that case the only thing to do is delete the wfw*.sys file and reinstall wfw.

Accepted Solution

05.02.1997 at 08:23PM PDT, ID: 1775251

gprichar:

Looks like it IS password protected. What's the shortest path to overriding it without destroying the desktop and appls installation?

05.03.1997 at 01:04AM PDT, ID: 1775252

nylja:

You only have to delete the settingsfile (the default filename in the open file dialog box). Then reinstall wfwg and all your other settings is still there.

05.03.1997 at 11:09AM PDT, ID: 1775253

gprichar:

Thanks. Where is ADMINCFG documented?

05.04.1997 at 12:57AM PDT, ID: 1775254

nylja:

In the Resourcekit for Win311.

05.05.1997 at 09:01AM PDT, ID: 1775255

gprichar:

Thanks. I moved the wfwcfg.sys and reinstalled wfw and that did the trick.

20080716-EE-VQP-33