Is the ROUTE of my server OK? I have a working Windows Server 2003 but it is slow with filetransfer. Its most probably a DNSproblem, I am already busy with that. I got the feeling though that there is also something wrong with my routingtable. I want to exclude this as a possible error in the whole setup, so I can concentrate on other things. [Such as a possible wrong DNS-setup]. This is the situation: The signal enters the building with a ADSL2 connection from my ISP. It goes through a SIP-SPOOFED Speedtouch 780 modem. [De official SIP-Spoof mode which can be set when using the last firmware.] - Because of the SIP-Spoof de VOIP-part of the modem has been turned of. This is needed, otherwise the datagrams will be thrown away at the entrance of the modem. Anyway its functioning well. The modem became a transparant router for the network. - My Windows 2003 server Enterprise R2 is working on a reasonable fast computer with two NIC's, one for the WAN and one for the LAN. This because I want use the following roles: DHCP, DNS, NAT, Firewall, Printerserver, File-server, WINS-server and VPN, in a secure environment. - On the WAN-NIC of my server server I have set a static IP-address [80.100.186.175 - which I got from my ISP]. For the Default Gateway I used the IP-address of my ADSL2-modem. - I set the LAN-NIC to the addres 192.168.0.1 Without a Default Gateway [Microsoft aloows only one DG in one computer]. - I got a FTP-server working on the servers IP-addres which is perfectly functioning. - I cannot ping the static IP-address though, which seems to be normal with these kind of modems. I did try to open the ping ports in the firewall though, until now without success. This is not a problem though imo; I have a perfect working FTP-server and NAT is working relatively good [could be a bit faster though]. - The server is connected with five Windows XP clients. - The clients do have Internet, the speed is relatively good, but the nameresolution could be better. Probably due to a improper set DNS server. - Especially the internal traffic [inside the LAN]is slow. Probably the already mentioned improper DNS and/or other Windows Server issues. I am now working through all kinds of articles considering that subject. - The clients do nicely get there IP-address from the the DHCP-server. Also the DNS-addresses do arrive nicely on the NICs of the clients. - The modem is de actual Default Gateway. I edited its IP-address with use of a http-browser. I gave it the addres of the server minus 1, so it is in the same subnet [i.e. 80.100.186.174] and functioning in conjunction with each other. Because of this it will not be possible to see a possible website or something, on that address, but that address is (still) not in use at the moment. I know this is not an elegant solution, but when everything works stable, I will adjust the addresses manually with use of the register. - Hereunder you find actual print-outs of the server and the client. [The server is in english, and the client Dutch, but I think you will recognize the data anyway, and the routing table of the server is the most important for me. Please look at these prints with the question in mind: 'Is the routetable setup well in conjunctiong with Windows Server 2003.' IPCONFIG /ALL via de CLI of the server: Windows IP Configuration Host Name . . . . . . . . . . . . : ydserver Primary Dns Suffix . . . . . . . : yd.local Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : Yes WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : yd.local Ethernet adapter WAN NIC: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : VIA Rhine II Compatible Fast Ethernet Adapter Physical Address. . . . . . . . . : 00-13-D3-A8-D6-06 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 80.100.186.175 Subnet Mask . . . . . . . . . . . : 255.0.0.0 Default Gateway . . . . . . . . . : 80.100.186.174 DNS Servers . . . . . . . . . . . : 127.0.0.1 Ethernet adapter LAN NIC: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC Physical Address. . . . . . . . . : 00-0E-2E-B8-4C-BF DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.0.1 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : DNS Servers . . . . . . . . . . . : 127.0.0.1 ROUTE PRINT of the server: IPv4 Route Table =========================================================================== Interface List 0x1 ........................... MS TCP Loopback interface 0x10003 ...00 13 d3 a8 d6 06 ...... VIA Rhine II Compatible Fast Ethernet Adapter 0x10004 ...00 0e 2e b8 4c bf ...... Realtek RTL8139 Family PCI Fast Ethernet NIC =========================================================================== =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 80.100.186.174 80.100.186.175 20 80.0.0.0 255.0.0.0 80.100.186.175 80.100.186.175 20 80.100.186.175 255.255.255.255 127.0.0.1 127.0.0.1 20 80.255.255.255 255.255.255.255 80.100.186.175 80.100.186.175 20 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.0.0 255.255.255.0 192.168.0.1 192.168.0.1 20 192.168.0.1 255.255.255.255 127.0.0.1 127.0.0.1 20 192.168.0.255 255.255.255.255 192.168.0.1 192.168.0.1 20 224.0.0.0 240.0.0.0 80.100.186.175 80.100.186.175 20 224.0.0.0 240.0.0.0 192.168.0.1 192.168.0.1 20 255.255.255.255 255.255.255.255 80.100.186.175 80.100.186.175 1 255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1 Default Gateway: 80.100.186.174 =========================================================================== Persistent Routes: None IPCONFIG /ALL of the Windows XP client Windows IP-configuratie Host-naam . . . . . . . . . . . .: COMPUTERMIKE Primair DNS-achtervoegsel. . . . .: yd.local Knooppunttype . . . . . . . . . . : hybride IP-routering ingeschakeld. . . . .: nee WINS-proxy ingeschakeld . . . . . : nee DNS-achtervoegselzoeklijst. . . . : yd.local Ethernet-adapter LAN-verbinding: Verbindingsspec. DNS-achtervoegsel: Beschrijving . . . . . . . . . . .: Realtek RTL8139/810x Family Fast Ethernet NIC Fysiek adres. . . . . . . . . . . : 00-11-2F-71-0B-20 DHCP ingeshakeld. . . . . . . . . : ja Autom. configuratie ingeschakeld. : ja IP-adres. . . . . . . . . . . . . : 192.168.0.10 Subnetmasker. . . . . . . . . . . : 255.255.255.0 Standaardgateway. . . . . . . . . : 192.168.0.1 DHCP-server . . . . . . . . . . . : 192.168.0.1 DNS-servers . . . . . . . . . . . : 192.168.0.1 194.109.104.104 194.109.6.66 194.109.9.99 Lease verkregen . . . . . . . . . : dinsdag 15 mei 2007 16:15:08 Lease verlopen . . . . . . . . . : vrijdag 25 mei 2007 19:15:08 ROUTE PRINT of the client: =========================================================================== Interfacelist 0x1 ........................... MS TCP Loopback interface 0x2 ...00 11 2f 71 0b 20 ...... Realtek RTL8139 Family PCI Fast Ethernet NIC - Pakketplanner-minipoort =========================================================================== =========================================================================== Actieve routes: Netwerkadres Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.10 20 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.0.0 255.255.255.0 192.168.0.10 192.168.0.10 20 192.168.0.10 255.255.255.255 127.0.0.1 127.0.0.1 20 192.168.0.255 255.255.255.255 192.168.0.10 192.168.0.10 20 224.0.0.0 240.0.0.0 192.168.0.10 192.168.0.10 20 255.255.255.255 255.255.255.255 192.168.0.10 192.168.0.10 1 Standaard-gateway: 192.168.0.1 =========================================================================== Permanente routes: Geen TRACERT to WWW.XS4ALL.NL from a client: Tracing route to www.xs4all.nl [194.109.6.92] over a maximum of 30 hops: 1 47 ms 99 ms 99 ms dsl174-186-100.fastxdsl.nl [80.100.186.174] 2 9 ms 9 ms 10 ms 195.190.249.13 3 9 ms 10 ms 10 ms 42.10ge-5-0-0.xr2.d12.xs4all.net [194.109.5.113] 4 10 ms 10 ms 10 ms www.xs4all.nl [194.109.6.92] Trace complete. So, the main question is: Do I miss something in the Routingtable? Or is it OK and should I keep my hands of it, and should I look further in the DNS-direction? Every answer will be very appreciated. -Durdane- P.S. De IP-addresses of the modem and the server are fictionl, because of privacy reasons. [The 4th block of the IP-address > 80.100.186.x], it has been adjusted consistently in the shown printouts.

First off, this is a pretty bad idea from the get go. I like Microsoft products, even have been accused of being an agent of Microsoft on these forums hilariously, but aside from using ISA 2004/2006, I would never ever use a Windows machine as a firewall/NAT device. There are completely free Linux distros out there that are far more reliable, far more secure, have more features, far less costly (as in free), and require zero linux knowledge or experience whatsoever. http://www.ipcop.org for example is free, has a web based configuration menu, requires literally no linux knowledge or experience, easy config backup and restore, provides intrusion detection, web caching, and more. There are free/openBSD solutions for this as well. Or you could even buy a hardware device for as little as $50 in a SOHO router. In this scenario, probably the problem is you have your DNS server listening on the internal NIC, but you have your external NIC configured to hit itself for DNS, and your binding order is off. Don't put a DNS server on your external NIC config. Leave it on the internal NIC only. Also, move the internal NIC to the top of the binding order. Finally, use the real IP of the internal NIC as the DNS server IP, not 127.0.0.1. (Don't ask me why it works better that way, it's a weird Windows thing.) "Enough, enough bowing down to disillusion! Hats off & applause to rogues & evolution! The ripple effect is too good not to mention. If you’re not affected, you’re not paying attention!"

and these are wrong on the workstation 194.109.104.104 194.109.6.66 194.109.9.99 Imagine the power if you knew how to internet search

Hi Heropsycho, Thanks for the fast and thorough reaction! After I have the ROUTE all right, I will indeed decide if I am going to use an ISA server, or an in between router that does the job for me. Linux is tempting but then I need an extra computer since I will use the other service of WSK3. U2 thanks wanderer. Other people already reacted on the DNS-addresses that show up on the nic's of my clients. I had put them in DNS list of the DHCP server. I already removed them from there. As I understand now they have to be forwarded in the DNS-server. I will keep you all posted. Thanks again. -Durdane-