How do I set-up my home network?


I'm trying to set up a home network (with Interent Connection Sharing). The clients that I've just built using Win98SE (never seen the interent yet, nor have had ANY updates) loaded up fine. I'm using the default Windows Client for Microsoft Networks. It is working as it should, allowing me to do everything and recognizing itself in Network neighborhood.

This "server" computer, on the other hand, keeps giving me "WNetOpenEnum failed, result is 1222" when I right-click on network neighborhood and check system information. It does not recognize any network.

This computer has a modem in it (the client does not). It has also been treated to all the Windows Critical Updates.

I have Kazaalite++ on this machine, but have turned off file sharing. I'm also running Norton Systemworks on it.

I've gone through many different scenarios of NetBEUI and TCP/IP configurations trying to get this to go.

What am I doing wrong???



This question was answered on April 26, 2004. Much of the information contained herein may have changed since posting.

You must upgrade your operating system to windows xp Because win 98 does not support internet connection sharing Also you must upgrade internet speed to a minimum 128k I also suggest that you put in a harddrive with a minimum of 40 gb of space WNetOpenEnum failed This message means that there was a problem enumerating

the servers on the network Invalid socket (TCP/IP might not be loaded) W32Time is the Year 2000 Compliant Time Synchronization Service that takes the place of the old TimeServ utility The functionality is similar, however all non-compliant functions have been removed.

W32Time has 3 possible configurations:

Master Time Server: The first is the Master Time Server, which uses the Simple Network Time Protocol to talk to original Time Sources like those at either the US Naval Observatory or National Institute of Standards and Technology

Primary Time Server: Once you have at least one Master Time Server, you can create any number of Primary Time Servers for each Windows NT domain in your network The Primary servers poll the Master Time Servers in your network for the current time.

Secondary (Client Mode): All the rest of your clients can be set up as Secondary machines These machines broadcast to the domain for a Primary server, and the first Primary that hears the request responds to it A machine set up as a Secondary can only request time from a Primary, it can not get time directly from a Master Time Server.

W32Time will not allow a Master Time Server to use any special hardware to access an Original Time Source If your network requires that it dial up a Time Source over the modem or with an ISA board in your system, you will have to continue using the old TimeServ.

Removing TimeServ:

If the old TimeServ utility from the Windows NT 4.0 Resource Kit has been installed on the system, it will need to be uninstalled before installing and using W32Time.

From a command prompt, run �NET STOP TIMESERV� to stop the TimeServ Service.

Run �DELSRV TIMESERV� to delete the TimeServ Service.

Delete the following 3 files:




Installation instructions:

Log on to the system with local administrator privileges.

COPY W32TIME.EXE to %SytemRoot%\sstem32.

COPY W32TIME.INI to %SytemRoot%.

EDIT W32TIME.INI as necessary (see below for details)

Run W32TIME -AUTOMATIC or W32TIME -MANUAL, depending on how you want the service to start Setting the service to �Automatic� will automatically start the service each time you boot Windows NT Setting the service to �Manual� will require you to manually start the service when you want it to run.

If you decide to edit W32TIME.INI later, you must stop the W32Time service, run W32TIME -UPDATE from a command line to update the registry, and restart the W32Time service

Uninstallation instructions:

To remove the W32Time Service, you simply need to run �W32TIME -REMOVE� from a command prompt This will not delete either the EXE or the INI file from the system, but it will stop the service and remove all the registry entries.

If you want to remove W32Time completely from the system, you will have to manually delete %sytemroot%\w2time.ini and %sytemroot%\sstem32\w32time.exe.

Starting W32Time:

Once the machine has been properly configured, you need to start the service on each machine before it will start synchronizing the time There are a couple ways to do this:

Go to Control Panel, Services, Click on the �Windows Time Service� and click the START Button in that dialog box.

From a Command Prompt, run �NET START W32TIME�.

If you installed the W32Time service as Automatic, you can just reboot the machine, and the service will startup automatically.

W32TIME.INI Settings:

Since W32Time has multiple modes of operation, it is important to edit the W32Time.ini file to properly describe the necessary settings This section describes the necessary information to modify the W32Time.ini properly There are ten total settings in the W32Time.ini (a typical installation will only use from five to seven).


Type specifies whether the Service is working as a Master Server, Primary Server, or Secondary Client A Master Time Server resides on the local network (to minimize discrepancies due to network congestion) and acquires its time from an original time source via NTP A Master Server can only poll one NTP Server for the current time, but there can be multiple Master Servers in a network If you have multiple Master Time Servers on a network, it is wise to have them each pulling time from the same original Time Source to prevent discrepancies There must be at least one Primary Server per domain, but each Primary can pull its time from a specified list of Masters on the network The Primary Server listens for a Time Request broadcast (from a Secondary) on the network and responds to it with the current time A Secondary machine is any other machine in the domain It can broadcast out to its domain to get the current time The Secondary machines are the only ones that send out network broadcasts Both Masters and Primaries send messages to the servers they're configured for The advantage of this setup is that a Secondary can leave one domain, join another, and automatically get the current time from the new domain�s Primary Time Server, without any additional configuration done on the client side The TYPE value has 3 possible settings in this version: NTP, PRIMARY, or SECONDARY.


W32Time periodically resets the time Default resets occur two or three times daily If you wish to set the time every twelve hours, simply edit the W32Time.ini and change the �Period� to �2� To update every 8 hours, set the �Period� to �3� To update every hour, set the �Period� to �24�, etc.


A default entry in W32Time.ini is TASync=no It specifies that the TimeAdjustment flag in the system should be fixed and skew compensation allowed By default, Windows NT regularly syncs the time to the CMOS RTC (on 3.51 or later it only does this when time is off by at least one minute) By specifying this option on the first time set after each boot, the clock will run using only the 8254-based timer which has greater precision and can result in greater stability In this mode, skew compensation is possible (for error in the rate of the system timer) Of course, if CMOS sync is not disabled, the long-term clock will take on the characteristics of the CMOS RTC with poor precision Setting your time daily should result in a clock with maximum /-.45 second error (twice daily /-.22s, four times daily /-.10s, etc) Detailed skew compensation is not normally attempted when using a network source because of inconsistent delays over the network In such cases if you notice time drifting more with W32Time than you had experienced before, you might want to set TASync=yes Warning: For skew compensation to work properly, you should never set the time manually while W32Time is running If you must set the time manually, either stop the Time Service first (and restart it after, if desired), or set TASync=yes.


NTP is the Network Time Protocol, using IP usually over the Internet W32Time only uses a Simple adaptation of NTP, so should not to be confused with the accuracy and reliability of the full NTP An NTP server must be specified (there is no default) �BroadcastClient� and �MulticastClient� are reserved names and can�t be used for NTP Servers.


When W32Time is running, it places any errors, warnings, or other information into the Application Log in the Event Viewer Therefore you should start Event Viewer and select Application Log to review the operational status If there are no events in the log, W32Time should be running fine If desired, an option is available to write an event in the log for successful syncs with an NTP Server (Log=yes in W32Time.ini) This option only works if TYPE=NTP in the W32Time.ini More information on the event description appears later in this document


Another option for setting up your Master Time Server is to also act as a Simple NTP Server to other Master Time Servers You enable this option by setting LocalNTP=YES in the W32Time.ini.


PrimarySource lists the NetBIOS names of all the Master Time Servers in the network Each name must be prefixed with 2 backslashes (\\) and names are separated by semicolons (;).


By default, a Primary Server will look at the list of Master Time Servers and attempt to contact each in the order listed on the PrimarySource line By setting RandomPrimary=YES, W32Time will choose one of the Master servers at random.


The TimeSource key should only be turned on when setting up a Primary server It tells the server to listen for Time Request broadcasts from the clients It is feasible to set a machine as a Primary, but not act as a Time Source You can get the current time from each of the specified Master Time Servers on the network without being bogged down with client requests Considering the dynamic nature of W32Time, this isn�t recommended.


SecondaryDomain tells a Secondary machine which domain to broadcast its Time Request to If you leave the entry blank, the Secondary machine will query its own domain for time information This is very helpful in a Master or Multiple Master domain model, where the Network Administrators don�t want to set up each domain with its own Primary Time Server(s).

Caution - contacting a distant domain might lead to time discrepancies depending on network traffic.

Need Help with this Issue?

We help people with technology! It's what we do.
Schedule an Appointment with a location for help!


Posted by Raymond of Katharine Gibbs School - New York on April 26, 2004