Your location:Tech News>OS>Window 2003>Windows 2003 system uses SyGate proxy Internet access failure

Latest News

Windows 2003 system uses SyGate proxy Internet access failure

Author:fsadmin

Views:

The school computer room recently upgraded the system to Windows 2003. In order to strengthen management we gave up the ICS sharing that comes with Windows and used SyGate proxy to share Internet access. Unexpectedly a series of problems appeared in the process of use and the author was quite a bit thinking about it.

Fault 1: After enabling SyGate all student computers in the school can share Internet access but the server can access the Internet when it is just turned on but cannot access the Internet after a few minutes.


The prompt box that pops up after configuring multiple gateways

< P>Cause analysis: Since the student computer can access the Internet it indicates that the network is connected. We switch to the connection sharing that comes with Windows and everything is normal. It is inferred that the cause of the failure is probably a SyGate configuration problem. However no matter how the settings are changed the fault still exists.

At this time the author suddenly thought of something: When configuring the IP addresses of the two network cards and other information we set the respective gateways to different values and when the settings were completed there was something like The dialog box shown. SyGate is a gateway-like proxy software. Is there a problem with SyGate because two gateways are configured in the network card properties? So we restarted the computer after deleting the gateway of the internal network card in the network settings and the fault disappeared.

Fault 2: After the above-mentioned faults are resolved the server runs stably. We make full use of the management functions of SyGate to manage the computer room in an orderly manner. However one day I suddenly found that the server and some computers could ping each other but they could not be accessed through Network Neighborhood ().


Failure diagram

Cause analysis: The computer that cannot be connected to the server belongs to For the 10.1.13 network segment we suspect that the network card with IP address 10.1.13.3 has a problem. Therefore after uninstalling this network card we replaced it with a new network card and reset it and the fault remained. Since they can ping each other there should be no hardware problems so the focus of detection is on the settings of the network card and the configuration of the network management software.?Fourteen ways to speed up Windows 2003 system ****

Recommend article

Relate article