Networks

Ask something
Question Locked

Slow Internet is it DNS problem?

0 helpful
6 replies

by naderihadi

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi

Here is the problem
We have a server SBS2003 and about 10 XP clients connected to the server.
in terms of connectivity, the inernet comes to the router first. The router then goes to the server and then from the second ethernet card on the server it comes out to the switch to be distributed.
Now interestngly, the internet seems very slow on the workstations. This is not the case when i connect a workstation directly to the router.

Our router also is a Gateway2Wire from BT.

The Lan connection on the server are
internet Lan
Automatic (from router)

internal Lan (used for the DNS)
IP 192.168.55.1
Sub 255.255.255.0
Gateway: Void
DNS: 127.0.0.1

On the workstation are
Lan:
192.168.55.(whatever)
Sub: 255.255.255.0
Gateway: Either Void or 192.168.55.1
DNS: 192.168.55.1

Help is very much appreciated

Thank

6 replies

by naderihadi

The Server is configured act as a Domain controller for our clients, The clients are able to connect and login to the server with their individual username and password.

Now if it is a case of IP setting misconfiguration, what settings do you recommend I should use?

Thanks

by naderihadi

Yes it was a silly mistake of me. As I said on my last reply, I set up the DNS based on the SDSL line. When I checked the DNS forward on the server, it was pointing to the SDSL router, whilst there is no SDSL router.
Its now sorted.
Cheers everyone

by skdtech

If I am understanding your setup correctly, the workstations are all connected to the Server and have to funnel through the server to get to the router. Try placing the switch between the router and your server. Your server is acting as a chokepoint on the network due to all internet traffic having to pass through it to get to the router. Unless you have the server setup as a network firewall it should be safe enough to allow direct router access to the router. Also ensure that DHCP is not active on the router if you are supplying it from the Server.

by naderihadi

You are correct, the server is acting as a check point and firewall.
I have now tested the netowrk with a different internet line (SDSL) and it looks fine!!! The difference between the previous and this one is that, the SDSL line is an unmannaged router, but the first one isn't. The first one has its own firewall and control system.
The problem now is that SDSL line I used was only for test and I need to use the first line for our office.
I am thinking if I need to configure our DNS or IP seting.

Oh let me say this. When I was installing the DNS service on the server, it was initially conntected to the SDSL line. Since the line is very expensive we are moving to an ADSL line which is now the trouble.

Help appreciated

This discussion is closed to new replies.