Networking a WFW 3.1 to Domain - Computing.Net

Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home

Networking a WFW 3.1 to Domain

Original Message

Name: ssardam
Date: July 30, 2004 at 11:13:20 Pacific
Subject: Networking a WFW 3.1 to Domain
OS: WFW3.11
CPU/Ram: DX466

Comment:

How to map a drive to a windows 2000 server on a domain

Report Offensive Message For Removal

Response Number 1

Name: sizequeen
Date: July 31, 2004 at 19:39:02 Pacific
Subject: Networking a WFW 3.1 to Domain

Reply: (edit)

After making sure the proper accounts have been created.
Do this in a terminal(ha!):
NET USE X: \\SVRSHARING\SHARENAME /P
the /P is for persistent
The NET command is god in WFW.
Bye

Report Offensive Follow Up For Removal


WFW 3.11 to XP Problems Networking a Windows 3.1 cient PC wfw 3.1 - wfw 3.11 Win 3.1 to wfw 3.11 3.1 to work on a Network w/ 9x, Me, 2K?	Networking WFW 3.1 & WinXP Pro Networking Windows 3.1 to WindowsXP Win 3.1 to run on a 386 3.1 to 95 Networking Win 3.1 to Novell 4.11

Use following form to reply to current message:

Name: From My Computing.Net Settings E-Mail: From My Computing.Net Settings Subject: Networking a WFW 3.1 to Domain

Comments:

  Homepage URL (*): 
Homepage Title (*): 
         Image URL:

Data Recovery Software

My PC has been hijacked!

Lexmark 2600 Printer Issues

btk1w1 infected start here post

Unwanted message remians on screen

The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC