I'd like to disable this specific printer from being redirected without removing the 3rd party driver, as it works fine if its connected to a share i. I'd consider doing the following it's convoluted as all get out, but it should give you what you want :.
Create local printers on the Terminal Server or other server computer corresponding to each printer attached to client computers.
You have control of the print queue name using this method such that you can make the name appear as you'd like. You can set permissions on the queues to prevent users from sending jobs to the wrong printers if you so desire. You can completely disable client printer redirection, as well.
Some people do the "Local Ports" but I've found throughout the years that I have severe reliability problems doing it that way. My method basically makes the PC act like a really expensive "JetDirect" box Install the driver for the "cheap printer" and your issues will cease.
You can usually figure out the model from the errors in the event log. Sign up to join this community. The best answers are voted up and rise to the top.
This is useful, for example, if you want to run multiple subnets on the same physical network. In the dialog, enter the IP address and its associated netmask. Windows defaults the subnet mask to the natural mask of the IP address you entered. If the IP address is part of a block with a specifically assigned prefix-length or is a member of a subnet, the correct value must be entered manually.
Always verify that the subnet mask is correct to avoid connectivity problems that can be extremely difficult to resolve. Remove an IP address by highlighting it and clicking Remove. Refer back to the IP Settings tab in Figure In the dialog, enter the IP address of the gateway and select the routing metric that you want to assign to this route.
The automatic metric is determined by the characteristics of the network interface. The following route print command shows an example of this:. The details of the routing table are explained in Chapter 2.
In this case, we are only interested in the first two active routes. They both are default gateways as indicated by the fact that they both have destinations and netmasks of 0. Both of these gateways were entered into the configuration through configuration windows associated with the D-Link Ethernet interface on this sample system.
The interface is assigned the IP address The first gateway—the one assigned address Both routes are associated with the same interface, and both have the same metric. Given the routing table shown above, the system will attempt to use default gateway This discussion is only about default gateways. If a specific route to a destination is included in the routing table, it is always preferred over the default route for packets addressed to that specific destination. Both of the default gateways in the table shown above are reached through the same interface In the routing table shown below, a metric of 5 was manually entered for the The metric defines the order of precedence among routers that can reach the same destination.
The lower the metric, the lower the cost, and thus the more preferred the route. When multiple gateways are defined for a single destination, only one gateway is active at any one time. Windows Server uses the gateway with the lowest metric.
If multiple gateways have the same metric, Windows uses the first gateway listed. Only if the preferred gateway is down or otherwise not accessible does it attempt to use additional gateways. Specifying multiple default gateways has limited utility because it requires that more than one router be directly attached to the same local network as the host, and that more than one of those routers be capable of reaching all destinations. In many cases where there is more than one router on the network some of the routers only reach other internal networks and therefore are not suitable to be default routers.
It is simply not flexible enough because it can only be used to define default gateways. If static routes are required, use the route command, which is available through the Windows Server command interface. It lets you manually configure the routes in the routing table. The command syntax is:. Flush all of the routes from the routing tables.
If used with one of the commands, the table is flushed before the command is executed. Create a permanent route that is reinstalled in the routing table every time the system boots. The command field specifies the action that the route command should take. There are four command keywords:. The netmask is applied to the address provided in the destination field to determine the true destination of the route. If a bit in the netmask is set to 1 , the corresponding bit in the destination field is a significant bit in the destination address.
For example, a destination of If no value is specified for the netmask , it defaults to Assume we are configuring a system that has the IP address In the following example we add a route to the host In each case, the address mask determines if the route is interpreted as a network route or a host route.
After entering the new routes, we display the routing table with the route print command to examine our handiwork:. As the display shows, there are several more routes than the two we just entered. All of the other routes are part of the basic routing table, which is described in Chapter 2. The routes we are interested in are both listed in the Persistent Routes section of the route print display.
Routes added by the route add command will not survive a boot without the -p option. Use the -p option when you want to add permanent static routes to the routing table. The -p option is not used when the routes are installed for some temporary purpose, such as troubleshooting.
Note that the default metric used with the route command is 1. The default metric can be overridden on the route command-line using the metric argument, as in the example above. The sample system used in this example has only one network interface adapter.
All of the routes added by the route add command are associated with that interface. When more than one network interface is available, Windows selects the default interface for a route based on the gateway address used for the route. For example, if the gateway address shows that the gateway is on network To manually specify the interface a route should use, add the if argument to the route command-line.
The interface should be specified by its interface number—not by its IP address. The interface number is the first field displayed for each interface in the Interface List section of the routing table. On our sample system, the interface number associated with the D-Link Ethernet card is 0x The following route add command associates the route to network Use the route command only when your system requires complex static routes.
Most workstations use a single default route, allowing that default router to redirect packets as necessary. The client portion of DNS, which is called the resolver , must be configured on every system. To customize the resolver configuration, select the DNS tab , which is shown in Figure Additional DNS servers provide added redundancy, but they rapidly reach a point of diminishing returns.
Each server is queried in turn, but only after the server above it in the list fails to respond to the query. Each server is queried multiple times and each query is given a reasonable timeout. These timeouts add up if too many servers are placed in this list, which unnecessarily makes the user wait for the inevitable error message. If the servers are properly chosen, they are not all going to be down at the same time.
It is far more likely that multiple servers are unreachable at the same time because of a network problem or a local problem. Adding more servers to the list, cannot fix a network problem. Two well-chosen servers are adequate, and three are probably the most you want.
If you cannot contact any of three different well-chosen servers, the problem is not with the remote servers; it is with the network or your local system. Use the Add, Edit, and Remove buttons as needed to configure the list of servers. Use the up and down arrow buttons to arrange the servers in the order that you want them searched. When Windows needs to resolve an IP address, it starts with the first server on the list.
If that server is unavailable, it then tries the second server. If that server fails to respond, Windows continues to try servers in the order they are listed until it either is able to resolve the address or runs out of servers to try.
Two option buttons and a checkbox in the middle of the DNS tab are used to configure how Windows qualifies unqualified hostnames. An unqualified hostname is a hostname without an associated domain name. When the resolver builds a DNS query for an unqualified hostname, the hostname is extended to a fully qualified domain name before the query is passed to the name server. The domain name the resolver appends to the hostname depends on which options are selected.
In Figure , the sample value entered in this box is sales. The primary DNS suffix, however, is not configured through this window. It is configured on the Computer Name tab of the System Properties dialog.
In the System Properties window, select the Computer Name tab. Click Change to open the Computer Name Changes window. Figure shows this dialog. Given the values in Figures and , the primary DNS suffix for this system is plant.
If the checkbox had been selected with the settings shown in Figures and , a request for the IP address of mandy generates a query for mandy. The system does not, however, search example. No parent domains would be searched. Defining your own domain search list is the alternative to using the primary and connection DNS suffixes.
This enables the Add, Edit, and Remove buttons. Click the Add button to add a DNS suffix to the search list. For example, the standard port monitor supports a "paper out" error. The target device must support the LPR protocol. The default TCP destination port is The default TCP source port is a randomly selected open port that is greater than You can use a Web-based interface from any Internet-connected client to view the status of standard port monitor events.
For network-connected print devices, the standard port monitor is the optimal choice. Because of the large volume of e-mail that he receives, it's impossible for him to respond to every message. However, he does read them all. Next, right-click Network Neighborhood and select Properties.
Click the Services tab and click the Add button. The next window asks you to supply the path for the I directory. This step will save you time when you need to add or reinstall services, and it will help you get the job done a little faster. After a minute or so, the copy process will be complete. Once the server has restarted, take a few minutes and reinstall the version of NT Service Pack that was previously installed on this server.
For example, Compaq servers have this type of update. Begin the printer creation process by selecting Start Settings Printers.
0コメント