There is no problem mixing ATS and peer-to-peer connections, other than that you give up some of the benefits of ATS which would have come through eliminating the peer-to-peer sessions and drive sharing. But it makes very good sense if the main motivation is to provide an efficient means to connect remote WAN users. Some points to watch out for when mixing connection types:
| • | Make sure that you use the same QFLOCK.SYS file for both types of users. This is guaranteed if you use the same MIAME.INI file, but there is no law preventing you from having different MIAME.INI files for the different connection types. |
| • | Make sure your printer INI files all make sense for both types of users, or takes steps to make sure users know which printer INI files apply to them. (The ATS users must use printers that are defined to the server, and cannot use the DEVICE=PROMPT: option, while the peer-to-peer users must use printers that are defined to their workstations.) |
