I've recently installed a D-Link DGL-4300 router and D-Link DSL-300T ethernet modem and are having a few issues, and wondered if anyone could shed some light on them... I followed the instructions given in both manuals to get them set up: 1. Plug phone line into modem, ethernet cable from modem to to computer. Set modem up to connect, which it does without a problem. 2. Un-plug modem's power. Un-plug ethernet cable from the computer and plug into router's WAN port. Connect the computer to the router's LAN port. 3. Power-up the modem and wait for the ADSL to sync. Power-up the router. Now the fun starts... Everything works... for a while. The router configures itself to connect to the modem via DHCP, and both wired and wireless computers have network and internet access. IP address are allocated to all computers on the network from the router. After about 30 minutes, the wireless computers lose internet and email connection, but not network - the router sees the computers (lists them as being connected), the computers can see and browse the wired computers, have IM connection, can ping websites, etc., just no websites load and email won't connect. The wired computer works fine. As far as I'm aware no ports are blocked on the router. I haven't started playing with the GameFuel software on the router yet. I don't think the router is faulty because there is some wireless activity going on, and the fact that they can still get some net access at all. The wireless computers are getting a good signal, and aren't being moved when the connection goes funny. I've be doing some reading up over the past couple of days, and the closest I've found to a resolution to the connection problems is changing the modem to connect via bridge mode, and putting the connection information (username, password, connection type, etc.) in the router, but that doesn't work at all - the modem connects fine, but the router won't. You'd think that two products made by the same company that are suited to be used with each other would work, wouldn't you?! I'm at work at the moment so I can't add hardware revision and firmware version, I'll add this to the post once I get back home.
To me it sounds like the wireless computers are having DNS problems. When it happens next time, goto start>run>cmd> ping google.com and tell us the results. Then after that type ping 64.233.167.99, and once again tell results.
Yup, it was a DNS problem, mixed with a little DHCP problem (I think - wireless computers were jumping from 192.168.X.X IP addresses to 169.254.X.X IP addresses, or is that down to DNS too?). Seems to be working fine now - I stopped fiddling at 1.30am this morning with 3 wireless laptops and 2 wired desktops all connecting to the network and the internet. Next job is securing the wireless network
Seems like DHCP was giving up on the wireless clients and then by the clients defualting, it had no DNS servers. Glad you got it fixed.
