Internet Slow on Workstations

[kpotter54]

I was looking through the posting and I wa reading WWW or Web access so slow, but seem to be only web but there was no answer.

From our server there is no trouble access the Internet. But when one of the workstation try to access the Internet there is a hang time of about 15 to 20 seconds before the page is display. Any thoughts on what needs to be change?

Also we are not using the WWW proxy server for the workstation to access the Internet

[Pascal]

Are they using the WinGate Internet Client or NAT then? How is your DNS Server setup? (Do you use WinGate's DNS, do you have an AD DNS, etc.)

[kpotter54]

[quote="Pascal"]Are they using the WinGate Internet Client or NAT then? How is your DNS Server setup? (Do you use WinGate's DNS, do you have an AD DNS, etc.)[/quote]

We have never used the WinGate Internet Client or the NAT. We are using the DNS that comes with Windows 2003 Small Business Server. We were using the ISA 2004 but to many problems

[Pascal]

Ok, I'm a tad confused now. If you're not using Proxy (As per original post), not using WGIC and not using NAT - how are your workstations connecting to the internet through WinGate?

[kpotter54]

[quote="Pascal"]Ok, I'm a tad confused now. If you're not using Proxy (As per original post), not using WGIC and not using NAT - how are your workstations connecting to the internet through WinGate?[/quote]

We setup the user account and add the user to the Assumed Users with there IP's and workstation names

[Pascal]

Yes, but how do the workstations know the internet is out through WinGate? If you are not manually configuring a proxy for them, not using NAT (Default gateway or DNS) or using the WinGate Internet Client - how are they told to get to the net through WinGate?

It could be that your system is using automatic proxy discovery, which might explain at least part of the slowdown ...

[kpotter54]

[quote="Pascal"]Yes, but how do the workstations know the internet is out through WinGate? If you are not manually configuring a proxy for them, not using NAT (Default gateway or DNS) or using the WinGate Internet Client - how are they told to get to the net through WinGate?

It could be that your system is using automatic proxy discovery, which might explain at least part of the slowdown ...[/quote]

They use the DNS server IP address 192.162.XXX.XXX on the Local Area Connection. If the workstations do not have the IP they will not connect

[Pascal]

And the same IP for the Default Gateway? If yes, is the DNS Service also the WinGate machine?

[kpotter54]

[quote="Pascal"]And the same IP for the Default Gateway? If yes, is the DNS Service also the WinGate machine?[/quote]

Yes also for the Default Gateway. The WinGate in on the SBS DNS server

[Pascal]

Alright, then inadvertently you are using NAT. Just to be sure - did you install ENS when prompted during the installer?

If you did, do you have "Intercept Connections" checked on the WWW Proxy Service's Sessions page?

[kpotter54]

[quote="Pascal"]Alright, then inadvertently you are using NAT. Just to be sure - did you install ENS when prompted during the installer?

If you did, do you have "Intercept Connections" checked on the WWW Proxy Service's Sessions page?[/quote]

I check the WWW proxy server and I'm getting errors on the bindings and the sever will not start. Also the Intercept Connections is check

[Pascal]

Ah, so what else do you have listening on port 80? Are you running IIS on that server? (That could be the reason for the binding conflict) I'd suggest clearing that up.

However, when a client computer opens a connection now, how does it show in WinGate? I'm assuming it's two arrows swirling around eachother? (One purple, one pink)

[kpotter54]

[quote="Pascal"]Ah, so what else do you have listening on port 80? Are you running IIS on that server? (That could be the reason for the binding conflict) I'd suggest clearing that up.

However, when a client computer opens a connection now, how does it show in WinGate? I'm assuming it's two arrows swirling around eachother? (One purple, one pink)[/quote]

We are using the IIS for a customer web page and when you open a web page on a workstation it show the NAT: TCP Connection to XXX.XXX.XXX.XXX:80

What would be the steps to clear up the binding?

[Pascal]

By ensuring that IIS only binds to the network adapters it needs to provide service and by ensuring that WinGate is only binding to the adapters it needs by setting the appropriate binding policies.

[kpotter54]

[quote="Pascal"]By ensuring that IIS only binds to the network adapters it needs to provide service and by ensuring that WinGate is only binding to the adapters it needs by setting the appropriate binding policies.[/quote]

You are going to have to be a little more on how to go about making this happen

[Roderick]

Hi,

Can you follow this link and submit a support request: http://support.qbik.com/index.php?_a=tickets&_m=submit.

TheWingate support team will be able to guide you as to the setup you need to make.

Regards

[kpotter54]

[quote="Roderick"]Hi,

Can you follow this link and submit a support request: http://support.qbik.com/index.php?_a=tickets&_m=submit.

TheWingate support team will be able to guide you as to the setup you need to make.

Regards[/quote]

I'ts done

[Roderick]

Hi,

Someone will be in touch shortly.

Regards
Roderick