Windows 2003 server proper config w/ one NIC

[geoffmgreen]

Latest v5 Wingate with 50 user license installed on Windows 2003 server with ENS.

DHCP and DNS services are disabled in Wingate; we only need Internet access from client PCs mostly XP Pro and POP3/ SMTP server(which work fine right now)

Using DHCP from Windows 2003 Server & NIC statically set to
IP: 10.10.10.4
SM: 255.255.255.0
GW: 10.10.10.4

....and all client PCs get dynamically(DHCP and DNS from server):
IP: 10.10.10.x
SM: 255.255.255.0
GW: 10.10.10.4
DNS: 10.10.10.4

LAN works fine for file activity.

Internet Browser on client PCs are set to use proxy server 10.10.10.4 port 80 and this works but it is delayed and slow for a T1 line(it should fly).

Can you tell me what is missing here? searched knowledge base and would like to keep one NIC and simple.

There is a firewall with LAN side set to 10.10.10.199 (ISP DNS set in firewall) that connects directly to Cisco managed switch as does server NIC.

Wingate is bound to server NIC

Thanks in advance.

[adrien]

That GW setting on your NIC looks bad.

By having the Gateway IP the same as the interface IP, you are basically telling your local TCP/IP stack that all IP addresses in the universe are available locally on the network connected to the NIC (rather than going through another router).

So I am surprised that this machine would even be able to reach the Internet.

Unless it has another default route? What does your route table look like?

[geoffmgreen]

Hello.

You are right , as I had it recorded wrong.

Corrected server/ Wingate NIC:

Using DHCP from Windows 2003 Server & NIC statically set to
IP: 10.10.10.4
SM: 255.255.255.0
GW: 10.10.10.199 (firewall LAN side)

DNS:
Primary: Verizon DNS
Secondary: 10.10.10.4

I think it is just a simple setting for DNS in Wingate maybe?

Thanks.

Will look route table.