http://www.windowsitpro.com/authors/author/author/5354713/rsscomment/5354713en-USSun, 27 May 2012 06:16:23 GMTSun, 27 May 2012 06:16:23 GMThttp://www.windowsitpro.com/article/telephony/state-of-computer-telephony-97-beyond-the-expo#commentsAnchorSat, 30 Jul 2005 01:59:57 GMT
hello,its good for knowledge.You people are doing well,may ask u soometjing will u help? actually i m a student and making a final year project i want to know how i can play a pre-recorded message over telephone.waiting ur reply anxiously, my mailling address:faisalanwer786@yahoo.com]]>Anonymous User Sat, 30 Jul 2005 01:59:57 GMThttp://www.windowsitpro.com/article/telephony/state-of-computer-telephony-97-beyond-the-expo#commentsAnchorhttp://www.windowsitpro.com/article/printing2/printing-and-remote-access#commentsAnchorTue, 24 May 2005 17:47:56 GMT
roland garro]]>Anonymous User Tue, 24 May 2005 17:47:56 GMThttp://www.windowsitpro.com/article/printing2/printing-and-remote-access#commentsAnchorhttp://www.windowsitpro.com/article/telephony/computer-telephony-terms-and-technologies#commentsAnchorFri, 07 Jan 2005 07:37:44 GMT
as u noted here we can do a IVR system that lets u some information in the database through speech do u have code for that .if u have plz reply me]]>Anonymous User Fri, 07 Jan 2005 07:37:44 GMThttp://www.windowsitpro.com/article/telephony/computer-telephony-terms-and-technologies#commentsAnchorhttp://www.windowsitpro.com/article/telephony/7-tips-to-deploy-a-successful-ivr-system#commentsAnchorMon, 24 May 2004 01:24:19 GMT
it is a gr8 pointer and does not let u skip anything]]>Pranav Mon, 24 May 2004 01:24:19 GMThttp://www.windowsitpro.com/article/telephony/7-tips-to-deploy-a-successful-ivr-system#commentsAnchorhttp://www.windowsitpro.com/article/internet/wildcat-interactive-net-server#commentsAnchorTue, 22 Feb 2000 01:05:54 GMT
It may be worth a look to re-visit wildcat it is under new ownership and the system is being updated and improvements made to it weekly. Visit the new owner at www.santronics.com.]]>Todd Ccochrane Tue, 22 Feb 2000 01:05:54 GMThttp://www.windowsitpro.com/article/internet/wildcat-interactive-net-server#commentsAnchorhttp://www.windowsitpro.com/article/internet/internet-ras-o-mania#commentsAnchorFri, 13 Aug 1999 14:25:16 GMT
I liked Alex Pournelle’s “Internet RAS-o-mania” column in May. He presents logic for finding a good supplier rather than trying to fix the technical stuff yourself. (My business is helping people find and work with the right suppliers.) Using an ISP that has the same OS is a good idea. I tried several big ISPs, and none had NT knowledge. Why did Microsoft invent a new script language for RAS? I’ve set up network logons in about 15 scripting languages, and the RAS one is the most primitive, obscure, obtuse, least intuitive, and least useful. If only Bill had bought Wall Data and used Rumba’s script language. While looking at multimedia shows, can Alex watch for an NT music editing and playback suite that works? Most demos and beta products don’t work or don’t use NT’s multitasking.
--Peter Moulding, HelpNet, Australia]]>Peter Moulding Fri, 13 Aug 1999 14:25:16 GMThttp://www.windowsitpro.com/article/internet/internet-ras-o-mania#commentsAnchorhttp://www.windowsitpro.com/article/security/nt-security-setup-with-windows-for-workgroups#commentsAnchorFri, 13 Aug 1999 13:51:13 GMT
I enjoyed Alex Pournelle’s August column. However, he missed an easy solution to the password list problem in WFW. It ships with a utility, admincfg. exe, that modifies the wfwsys.cfg file. One option is to force a domain logon only, bypassing the local Windows password. I use this option at many client sites, and it eliminates the double password problem. From years of experience, I recommend that small workgroups set up the NT server as a domain controller. With NT’s user-level shares, this approach simplifies controlling access and eliminates the need for multiple passwords, so you can keep password problems to a minimum.
--Eric Rintell]]>Eric Rintell Fri, 13 Aug 1999 13:51:13 GMThttp://www.windowsitpro.com/article/security/nt-security-setup-with-windows-for-workgroups#commentsAnchorhttp://www.windowsitpro.com/article/security/nt-security-setup-with-windows-for-workgroups#commentsAnchorFri, 13 Aug 1999 13:38:19 GMT
Alex Pournelle’s August column, “NT Security Setup with Windows for Workgroups,” discusses the fact that Windows for Workgroups (WFW) has two levels of passwords. One opens the local .pwl file, which contains the cached copies of all secondary passwords to the resources that you use (domain passwords). If you change the password using Control Panel in WFW, the password changes on the .pwl file and not on the domain controller. This discrepancy causes many problems with users who believe that they are changing their password on the domain controller (when prompted), but they are not changing the domain password, just the .pwl password! Although three ways exist to fix this problem, Alex mentioned only one (the WFW loophole). A little-used and -known utility on the WFW installation disks (#8) called admincfg.ex_ (expand and create admincfg.exe) lets you control the settings in the wfwsys.cfg file in the c:\windows directory. You can enable or disable file and printer sharing, restrict network dynamic data exchange (DDE), and restrict access to changes to network settings. You need to run this program to disable password caching and save an updated wfwsys.cfg file. Another option is to add

PasswordCaching=No

in the [NETWORK] section of system.ini. You can find additional information in MS Windows for Workgroups Resource Kit 3.11, Chapter 5, “Security Control Enhancements,” and Microsoft Knowledge Base article # Q128910.
--Ron Melanson, MCP

Thank you for your comments. I had no idea other loopholes exist; it’s great when readers point out how much I have to learn.
--Alex Pournelle]]>Ron Melanson Fri, 13 Aug 1999 13:38:19 GMThttp://www.windowsitpro.com/article/security/nt-security-setup-with-windows-for-workgroups#commentsAnchorhttp://www.windowsitpro.com/article/security/nt-security-setup-with-windows-for-workgroups#commentsAnchorFri, 13 Aug 1999 13:27:44 GMT
In response to Alex Pournelle’s August column, Eric Rintell’s October letter, “Password Problems in WFW,” suggests using admincfg.exe to prevent local Windows passwords from being saved to .pwl files. While this solution works, it’s easier to add the following line in system.ini:
[Networks]
passwordcaching = no
--Andy Ball, MCSE]]>Andy Ball Fri, 13 Aug 1999 13:27:44 GMThttp://www.windowsitpro.com/article/security/nt-security-setup-with-windows-for-workgroups#commentsAnchorhttp://www.windowsitpro.com/article/internet/email-for-the-small-business#commentsAnchorThu, 12 Aug 1999 14:24:42 GMT
I just finished Alex Pournelle’s October 1996 column, “Email for the Small Business.” It is slanted, biased, and flawed. After working with NT, Microsoft Mail and Exchange for more than three years, I can address some items he mentioned.
I agree that little MS Mail documentation comes with NT, but you need only two resources: TechNet and Microsoft Windows NT Resource Kit for NT 3.51. TechNet articles describe the mail system’s architecture and troubleshooting steps. The NT Resource Kit devotes Chapter 8 (Volume 1: Windows NT Resource Guide) to the use of Mail with NT.
MS Mail’s security certainly is not C2 like NT’s. Unfortunately, only so much security can be built into a shared file system. You can, however, implement some security with MS Mail. Instead of simply stating it has none, why not offer the readers the option of sharing the postoffice (PO) directory by appending a dollar sign (e.g., WGPO$) to the filename. This step prevents the share point from appearing in any browse list. Users can then configure the clients with a universal naming convention (UNC) path for Serverpath= in the msmail.ini or Registry (depending on the OS). No permanent drive mapping is necessary. What users can’t see, they can’t delete. This capability is further enhanced in the FPP with the addition of a utility that will encrypt the path to the PO in a file, so it will be unreadable to the user.
Pournelle mentions that there is no way to create accounts from the NT User Accounts Database. Although that statement is true, he needs to point out that if the network administrator upgrades, the full packaged product (FPP) will not only allow import from the NT User Account Database, but also from a NetWare bindery.
Pournelle then begins to sell NetWare and NetWare Directory Services (NDS) because of its centralized management. NDS does offer many advantages compared to NT’s administration capabilities and domain model, but finger pointing is off target. Exchange Server provides this integration with network logon. Because Exchange relies on NT’s built-in security, the user’s password allows access to the network and the mailbox. In addition, through an extension that Exchange Server installs to User Manager, the creation and deletion of mailboxes is linked to the action taken on the user’s NT account. Note that this process also works in reverse with the Exchange Administrator program. Because of MS Mail’s older architecture, this capability was not a programmable option. I don’t believe NDS was available in the late 1980s and wasn’t well developed until 1995.
The postoffice pointer is in the Registry under HKEY_CURRENT_USER\SoftwareMicrosoft\Mail\Microsoft Mail. ServerPath : REG_SZ : C:\WGPO. Because each user can create a PO, the option is stored under each user’s Security ID (SID) rather than HKEY_LOCAL_MACHINE. The only difference between connecting to an existing PO and creating a new one is the ability to run Postoffice Manager.
As for removing the WGPO, the process is published in Microsoft’s Knowledge Base as Q104021. You just have to delete the directory from the hard disk and the reference in the Registry noted in the previous paragraph. You can find this article on the Web at http://www.microsoft.com/ kb/articles/q104/0/21.htm.
Yes, the client gives the option of an offline address book (OAB), but it can use the global address list (GAL) on the server. The client gives you an OAB to use when you can’t connect to the server; this offering is a bonus, not a drawback. Some of us need this functionality. In fact, I’m taking full advantage of it right now on a flight from Houston to Boston. As a side note, the file downloaded for the OAB is the same as that for the MS Mail Remote client, rnetwork.glb. Care to complain about that client, too?
Pournelle next comments on the fact that the client must poll the server to check for new messages rather than using a remote procedure call (RPC) from server to client when new mail arrives, as in Exchange Server. It’s the Microsoft Mail information service within the client that has this limitation. This service acts the same as the MS Mail client does. How can a passive shared file system contact an active client? Again, it all goes back to the architecture.
I’m sorry Pournelle doesn’t like the interface of the Windows Messaging (WM)/Exchange clients, but he may be happy to know that Outlook (in Office 97) has a completely different UI.
Pournelle seems to expect features that are not possible with MS Mail’s architecture. Rather than complain that they don’t exist, he could help the readers to understand what the environment does provide, explain workarounds, and inform about alternatives that are strong in the areas where MS Mail is weak.
Please share this information with readers. The magazine is one of the best I’ve read, and I hate to see it damaged by articles like this one.
--Dan Nelson, MCSE, MCT, CNE
NT/Exchange Consultant

Thank you very much for your informative and helpful corrections. We’re always grateful when readers keep us on our toes!
--Karen Forster]]>Dan Nelson Thu, 12 Aug 1999 14:24:42 GMThttp://www.windowsitpro.com/article/internet/email-for-the-small-business#commentsAnchor