Tag Archives: DSL-G604T

dlink dsl-G604T doesn’t like firefox

Computer Aid Posted on by

A customer was having problems getting his wireless router (dsl-g604t) to make a wireless connection (he likes to experiment, and thinks he stuffed up a setting somewhere).

He had one PC connected to the router via ethernet. I try it and I can see the router. I can connect via his default browser (firefox), and I change some settings.

I then go to save and restart. I push the button, but the router LEDs continue to glow and blink as usual. I expect most of them to switch off, at least temporarily, but nothing happens.

I try pulling the power plug, but when I reconnect to the router, none of the settings have changed… hmmm

I try just one setting (the SSID), restart the router, and the old SSID is back after the restart. A faulty router?

I try changing a few other settings, but the results are the same…

I eventually decide to try IE instead of firefox. I change the SSID again, press the save and reset button, and hey!, a small window pops up (blocked by firefox), that asks “are you sure?”

After that hiccup, I setup WPA-PSK (I have no option to choose AES encryption, so I use TKIP instead)

I setup the laptop, and I setup the second PC (it also has wireless).

The only task left is to take a look at why the printer is not working. The printer seems to have the drivers installed correctly, and an appropriate windows printer exists.

I go to print a test page, but I get some pages with funny characters printed on them instead.

I see there are about 6 jobs n the print queue. I cancel them all, but the jobs currently printing doesn’t want to be cancelled… even after a PC restart.

In the end, I just let the printer complete its job, restart the PC and the printer, and everything is working normally.

And all done within 1 hour. Its amazing how much (and sometimes, how little) can be accomplished in just 1 hour

adding a dlink dvg-2001s voip adapter to a DSL-G604T router

Computer Aid Posted on by

A customer was struggling to get her new dlink dvg-2001s voip adapter to work with a new dlink dsl-g604t wireless modem-router.

Since she is using a laptop over an unsecured wireless link, I decide to first get the wireless working securely.

I connect to the router, change it to WPA–PSK(as usual, the router doesn’t tell you if it will use WPA-PSK-TKIP, or WPA-PSK-AES)… So after restarting the router, I find I cannot connect using either TKIP or AES. But its happened to me before: its just a case of being patient.

In the meantime, I take the laptop over to the DVG unit, and connect to it via ethernet cable (disconnecting it from the router).

But I can’t connect to it. I cant even ping it.

I manually enter the appropriate IP settings for windows and then restart the PC and the DVG.

But I still cannot connect to it. I figure the customer must have mucked up something while trying to get everything going. So all I can do at this stage is reset to factory defaults.

I can connect now. Since the DVG happens to default to the same IP address as the DSL-g604t, I decide to try something simple: I change it to a fixed IP (10.1.1.253… it was 10.1.1.1).

But now I’m back to where I started: I cannot connect to the DVG… So, factory reset again, and then do the job properly, get it to obtain its IP address from the router, and configure the router to always give a specific address to the DVG. I pick address 10.1.1.222.

So, I connect the PC to the router, connect the DVG to the router, power-cycle everything, then connect to the router and see whats going on (the wireless network still hasn’t kicked in yet… So I’ll look at that again).

Looks like the wireless security is now on WEP… I’m sure I set it to WPA… So I set it back to WPA, apply the change, go to settings, click “save and reboot”, click on reboot button (dlink should rename these buttons: are you sure… are you really, really sure… etc).

After the restart, XP detects the wireless network… at last.

I try connecting to the detected wireless network, but it fails (both tkip and aes)… I connect to the router again, and I see it is still on WEP… I repeat this cycle about 3 times, until the WPA settings finally “stick” Grrr.

Ok, I get XP to connnect (after restarting XP and waiting a few minutes…)

I now unplug the ethernet cable between the PC and the router , restart the router and laptop, and look forward to some wireless computing from a more comfortable position.

But when XP restarts, It doesn’t find the wireless network anymore… Huh?

I go over to the router (I’m almost ready to yell at it!). Hold on, the router WLAN light is off… it shouldn’t be off. All the other light are working correctly. Why has only the wireless decided to fail?. Anyway, I try restarting the router (again! except this time, I wait 15 seconds before reconnecting power).

OK, the WLAN light comes on now…

The laptop connects to the router correctly again.

I setup the router to hand out IP address 10.1.1.222 only to the MAC address of the DVG adapter, so it should always have that address. I save the settings and restart the router and the DVG.

I then setup the router “virtual server” (otherwise known as port forwarding), so that port 5060 is allowed to pass through the router firewall, to the dvg adapter. Save and restart.

Once I’m sure all the settings are correct and I can connect to both the router and the dvg, I then try the voip phone… I hear a dial tone, but cannot call out…

Now we call the voip company, and it turns out the DVG was pre-configured with the customers details (passwords, etc) (all lost after the factory reset). So we connect to the dvg and enter the correct details and restart it.

pressing **1 on the phone gets the dvg to “speak its IP address” to you over the phone… neat.

Anyway, we make a call, and it seems to work.

I thank the voip technician, and a short while later, try to call my mobile… there is a disconcerting delay between the mobile ringing, and the voip phone sounding a ringing tone. I hangup the voip phone, but my mobile keeps ringing… what?

OK, I’ll power-cycle everything again, just to be sure.

But now, the voip phone doesn’t play a dial tone then the receiver is lifted… I start hearing Yoda saying “patience young jedi”… but I snap out of it when I hear the phone make a short ring… hmmm

I eventually figure out that once the DVG is up and running, it will usually take 1 or 2 minutes before it logs in to the voip server (and gives a quick ring when the phone is ready to be used)…

Some instructions on all this would have been nice!

Anyway, after the power-cycle and the delay waiting for the voip to activate, everything seems ok. I try ringing a few numbers and it’s all working well (at last… after 3.5 hours!).

Remote desktop testing on DSL-G604T

Computer Aid Posted on by

This customer had previously asked me to setup remote desktop, so that a software vendor could connect and update its software remotely.

I had previously setup the port forwarding (d-link call it: virtual server) to allow port 3389 to pass through to the main PC.

Also had to disable the windows firewall (asked to do so by the software vendor), in order to allow access. I’ve since found the correct way to bypass the windows firewall without disabling it!

A week later, I’m told that remote desktop access is no longer working… Grrr

I take a look, and I see that the main PC now has a different IP address… So I connect to the DSL-G604T router and then setup for a fixed IP address. I also setup the PC with a fixed IP address (not using DHCP)… it takes a while, but eventually, everything is working correctly.

I try remote desktop from a second PC (to the internal LAN IP address) and it works well.

I try using the same PC to connect to the “external” fixed IP address… but no go.

I try many different variations, but still no go.

By looking at some online help, I see some mention of the need for a firmware upgrade. I’d like to avoid this if I can, so I keep searching. I also find a vague mention that you cannot use remote desktop to control a “remote” PC, if that PC is on the same LAN(ie I cannot “go out to the internet” and then “connect back in”).

So I call my wife and ask her to try connecting from the office PC… But it doesn’t seem to work. She eventually realises that I didn’t say to put a dot between the first and second IP numbers (Doh!)… but even after that has been corrected, it still doesn’t work.

At this point, I’ve been onsite for 4.5 hours, and I’m running out of ideas. I decide to try ultraVNC, but don’t have time to test it… I promise to return, once I have a solution.

Once back at the office, before trying VNC, I take a look at RD, … I hit the options button, and I notice the domain is set to “martindom”… I clear the domain field, hit the connect button, and I’m surprised to see that I’m connected.

I quickly call the customer (and apologise for disrupting their PC while they are working) and tell him that the PC is finally able to be updated.

I login a few days later and disable VNC, and I email the customer, strongly advising that he updates his passwords, as they can easily be guessed.

Looks like RD cannot be properly tested without using a remote site…