Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[EddieZ]

Not that I doubt you, but are you sure a. the modem behind the router (or your local firewall) isn't blocking VOIP or b. does it work when you configure the needed ports manually (portforwarding or virtual server)?

[creat0r79]

ok, took the plunge
problem,saved firmware on 1.11eu, tried to load it with 1.21, invalid config  $#@#$@#@$ (curses...). ow well, guess it's time to rebuild....
problem 2, these devices
ssid   001DE064B587   192.168.0.103   802.11n (2.4GHz)   130   86
ssid   00195B109E46   192.168.0.100   802.11n (2.4GHz)   54   76

basically the 192.168.0.103 is a laptop on a table with a n card (ok 130 is normal, and perfect), .100 is a dwa 142 in a pc, and it's on the table as well - so same distance, (it's ina pc), with it i'm getting very low rates, 13,27,54... (the device itself, in windows says 270-300), problem is this one:

ssid   001B11705EF7   192.168.0.101   802.11n (2.4GHz)   65   56

an identical 142, placed at maybe 15 meters away,through a concrete wall (between the first two and the outer, there's like 5 meters and no walls)

wlan to wlan speed transfer speed (for those) is about half of what i usually see
also, i can't see the gateway connection in network connections under xp anymore

i reflashed 1.11, speed is back now, but the gateway connection is still missing 

[TheXman]

One thing I noticed about 1.21b05 is that every second it sends a UDP broadcast to 239.255.0.1.  Each broadcast increments it source ports by one.  I've watched it increment its source port from port 4100 thru 4120 before stopping the sniffer trace.  After I saw this behavior, I reloaded 1.20.  1.20 does not send these broadcasts.  I don't have any multicast or uPNP options enabled.  This is odd behavior.  Does anyone know why it is doing these UPD broadcasts to 239.255.0.1?
--
Xavier

[steve_wch]

OK, last night I was able to flash back 1.21 to test my DNS saga...

I found this option "Enable DNS Relay" under (set up-->network setting) makes a difference in my case.
It is default to enable in my case.   For some reason, with DNS Relay is enabled the routing is not stable.  It started with the win2K PC trying to access web and failed; after that other PC's access to same address will get incorrect routing.  I disable this option; so far so good.

I did a trace route for both pass and fail case: note the IP address is resolved correctly for the website (70.42.142.20); but routing has some issue after 3rd hop.

(ok)
Tracing route to www.linkedin.com [70.42.142.20]
over a maximum of 30 hops:
  1    10 ms     9 ms    10 ms  bras24-l0.pltnca.sbcglobal.net [151.164.184.91]
  2     8 ms     8 ms     8 ms  64.164.107.1
  3     8 ms     8 ms     8 ms  69.220.8.95
  4    10 ms     9 ms    10 ms  69.220.8.31
  5    17 ms    11 ms    12 ms  ve318.fr4.sjc.llnw.net [208.111.152.117]
  6    13 ms    12 ms    12 ms  linkedin.ge3-4.fr4.sjc.llnw.net [208.111.152.102]
  7    13 ms    14 ms    15 ms  www.linkedin.com [70.42.142.20]

(fail)
Tracing route to www.linkedin.com [70.42.142.20]
over a maximum of 30 hops:
  1    11 ms    11 ms    11 ms  bras24-l0.pltnca.sbcglobal.net [151.164.184.91]
  2    10 ms     9 ms    10 ms  64.164.107.2
  3     8 ms     9 ms     8 ms  151.164.93.239
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
....

My hardware version is A3; when DNS Relay is enabled, all PCs' DNS server point to 192.168.0.1; when disabled,  DNS server point back to ISP.

Best,

Steve

[EddieZ]

OK, last night I was able to flash back 1.21 to test my DNS saga...

I found this option "Enable DNS Relay" under (set up-->network setting) makes a difference in my case.
It is default to enable in my case.   For some reason, with DNS Relay is enabled the routing is not stable.  It started with the win2K PC trying to access web and failed; after that other PC's access to same address will get incorrect routing.  I disable this option; so far so good.

I did a trace route for both pass and fail case: note the IP address is resolved correctly for the website (70.42.142.20); but routing has some issue after 3rd hop.

(ok)
Tracing route to www.linkedin.com [70.42.142.20]
over a maximum of 30 hops:
  1    10 ms     9 ms    10 ms  bras24-l0.pltnca.sbcglobal.net [151.164.184.91]
  2     8 ms     8 ms     8 ms  64.164.107.1
  3     8 ms     8 ms     8 ms  69.220.8.95
  4    10 ms     9 ms    10 ms  69.220.8.31
  5    17 ms    11 ms    12 ms  ve318.fr4.sjc.llnw.net [208.111.152.117]
  6    13 ms    12 ms    12 ms  linkedin.ge3-4.fr4.sjc.llnw.net [208.111.152.102]
  7    13 ms    14 ms    15 ms  www.linkedin.com [70.42.142.20]

(fail)
Tracing route to www.linkedin.com [70.42.142.20]
over a maximum of 30 hops:
  1    11 ms    11 ms    11 ms  bras24-l0.pltnca.sbcglobal.net [151.164.184.91]
  2    10 ms     9 ms    10 ms  64.164.107.2
  3     8 ms     9 ms     8 ms  151.164.93.239
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
....

My hardware version is A3; when DNS Relay is enabled, all PCs' DNS server point to 192.168.0.1; when disabled,  DNS server point back to ISP.

Best,

Steve

To my knowledge, when DNS Relay is disabled, the DNS does notpoint back to the provider... In that case you need a visible DNS server on the LAN to do DNS queries. At least that's what the Help item says...

[chaicka]

One thing I noticed about 1.21b05 is that every second it sends a UDP broadcast to 239.255.0.1.  Each broadcast increments it source ports by one.  I've watched it increment its source port from port 4100 thru 4120 before stopping the sniffer trace.  After I saw this behavior, I reloaded 1.20.  1.20 does not send these broadcasts.  I don't have any multicast or uPNP options enabled.  This is odd behavior.  Does anyone know why it is doing these UPD broadcasts to 239.255.0.1?
--
Xavier

Probably you may want to check this out:
http://www.faqs.org/rfcs/rfc2365.html

Multicast...Hmmm.

[TheXman]

Probably you may want to check this out:
http://www.faqs.org/rfcs/rfc2365.html

Multicast...Hmmm.

Okay, I just read the document you referenced entitled RFC2365 - Administratively Scoped IP Multicast.  Now what?  You didn't and it doesn't answer my question.  And yes, it is a multicast.  What was your point?  My point is that it wasn't doing this in v1.20 and I wanted to know why it was implemented and what exactly is it doing.

[wiak]

you might want to try OpenDNS instead of your ISPs
http://www.opendns.com/

[lotacus]

Well, i'm glad that dlink is listening to it's customers and make better use of the usb port.

there are a couple other features I'd like to see which i've emailed  them about, one really useful thing would be to remove the SSID name in the wireless connection status page and replace it with the computetr name so it would be easier to determin which computer is having rate/signal issues, rather than having the inconvenience to navigate away from the page to try and find which computer it is.

As for the securespot addition, it's a welcomed feature, though I most likely won't have any use for it other than the anti-virus feature. One question does come to mind though is where that 30 dollars a year is going and what is it being used for. The only updates I can see to come from the software is the definition updates. However, i suppose 30.00 a year is adequate, and i'm sure there are a lot of people that would use all the features.

The transfer rate does seem to be slower than the norm for the storage feature, which could be attributed to one or both of the following: USB port is 1.1 and the router or the shareport software could be limiting the bandwidth through some throttling or QOS method. I tested several large files, rar, zip, exe, iso, mkv, ts, avi etc, and performace was all the same. A couple instances, I did see a huge increase in performance at about 58MB per second using a maxtor onetouch usb drive, but furthar testing made me suspect that the speed was due to windows write caching, thinking that the entire file had already been transfered, when in fact it wasn't. This could potentially cause a problem if the usb drive isn't unmounted after the transfer has really completed, leading to data curruption, if one were to remove the drive or if another user took over the session.


For those wondering how it interfaces, it indead would need to be using a TCP method since wireless devices would need to access the device as well.

After the upgrade, I did have to hard reset the router to successfully apply the saved configuration settings. (hard resets are always recommended) and had to reboot the gateway because for some reason the PPOE connection wasn't being established.

Noticed that after making a change, for example, to port forwarding, the router would seem like it reboots, but when it returns to the screen my PPOE connection doesnt connect anymore. I press reboot router on system screen and it still doesnt connect. I Have to manually pull the power cord our of the router.

Minor set backs, but overall thumbs up for dlinks move to push this routers use to a new level.

[lotacus]

btw, the software uses port 20005 to communicate as determined by
netstat -b

TCP    192.168.0.3:21176      192.168.0.1:20005      ESTABLISHED

attempts at ftp, tftp, ssh etc, disconnects the session, disconnects the drive, disables the software, then it re-enables.

I imagine it's using some proprietary connection.

[barich]

Shared printing is still broken.  It was broken in 1.20 as well, but not in 1.11 or 1.11_MSBETA.

Symptoms: Attempting to print or open printer properties takes a long time (several minutes or more).  Word will freeze on launch for a period of time if the default printer is experiencing this problem.

Operating system: Vista x64 for sure, may affect other OSs

Steps to reproduce: Have a shared printer on a computer running Windows Vista.  Install this printer as a network printer, either using the add printer wizard or by typing the UNC path of the computer (i.e. \\COMPUTER) into Explorer and double-clicking on the printer on another computer running Windows Vista.  Attempt to print, or view the printer properties.  Either dialog box will take several minutes to appear.  Several minutes pass before printing begins once the "print" button in the dialog box is clicked.  File sharing with the same computers works fine.  Reverting to firmwares older than 1.20 work fine.

Please fix this!  I like the new features that are being added, but I can't use them, becaues I have to use older firmware merely to be able to print.

[EddieZ]

Shared printing is still broken.  It was broken in 1.20 as well, but not in 1.11 or 1.11_MSBETA.

Symptoms: Attempting to print or open printer properties takes a long time (several minutes or more).  Word will freeze on launch for a period of time if the default printer is experiencing this problem.

Operating system: Vista x64 for sure, may affect other OSs

Steps to reproduce: Have a shared printer on a computer running Windows Vista.  Install this printer as a network printer, either using the add printer wizard or by typing the UNC path of the computer (i.e. \\COMPUTER) into Explorer and double-clicking on the printer on another computer running Windows Vista.  Attempt to print, or view the printer properties.  Either dialog box will take several minutes to appear.  Several minutes pass before printing begins once the "print" button in the dialog box is clicked.  File sharing with the same computers works fine.  Reverting to firmwares older than 1.20 work fine.

Please fix this!  I like the new features that are being added, but I can't use them, becaues I have to use older firmware merely to be able to print.

I have no problems printing (1.20, 1.21). Just can't reproduce...No delays or whatever...I use Vista x86, maybe that's the issue?

[Alemaker]

Nope-serious issues here with shared printing also-running 2 machines with Vista Ultimate x86. Have an HP 8180 all-in-one connected to the desktop x86 Vista machine via usb and cat5'ed to the router. When I try and print any Office docs from my laptop running x86, I get the same thing as the above poster. Hangs Office-not acceptable performance at all. Back to 1.11. Lycan, you guys need to look into this as this issue is present in 1.20 and now continues in the beta 1.21B05 

[EddieZ]

Perhaps you can give a list of all your settings so the Dlink guys can reproduce the issue (use the .gws).

[whalethewise]

Hi

I still have an issue with creating schedule. Weird but I cannot create schedule when it goes through the 2 AM and end time is less then 10 AM.

For example,

cannot create schedules

1:0 AM - 8 : 0 AM
2:0 AM - 4 : 0 AM

but I can create
1:0 AM - 2:AM
3:0AM - any time

Most interesting that I can create schedule 1 AM - 2:46AM but cannot create 1 AM - (any time after 2:46 AM)

Weird that 2:46 AM - 2:47 AM is a point of error

Thanks