• September 24, 2017, 09:17:23 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Pages: [1] 2 3 ... 10
 1 
 on: Today at 11:58:43 AM 
Started by Inner - Last post by Inner
using 2 DSR-150's one as client and one as server  US. A3 2.11WW

created a PPTP tunnel and it works fine except that I cant see the Client Devices, but the Client Devices can see the Server devices.
I tried swapping WAN on the server and client to see if it was ISP specific and same issue.
I tried swapping the profile... turned the client into the server and the server into the client and same issue.
has anybody come across this issue ?


 2 
 on: Today at 10:40:10 AM 
Started by georgeorgeorge - Last post by FurryNutz
Let us know if you find out. The OP hasn't been online for 3 years now.  ::)

Might send him a PM and see if he returns...

can you share on how this was completed? Also what is the performance like - looking to decommission the NVR and want NAS only. New cameras installed.

 3 
 on: September 23, 2017, 07:23:07 PM 
Started by georgeorgeorge - Last post by roccoizm
can you share on how this was completed? Also what is the performance like - looking to decommission the NVR and want NAS only. New cameras installed.

 4 
 on: September 23, 2017, 01:04:55 PM 
Started by NDLBox - Last post by FurryNutz
Ok, let us know what they say.

 5 
 on: September 23, 2017, 01:03:46 PM 
Started by NDLBox - Last post by Mr.Navy
Copied - This symptom of lowering the Resolution refers to ALL cameras, not only one (sorry for being unprecise)

Sounds like a problem with the NVR and the one camera its changing. I recommend that you phone contact your regional D-Link support office and ask for help and information regarding this. We find that phone contact has better immediate results over using email.
Let us know how it goes please.

 6 
 on: September 23, 2017, 12:58:37 PM 
Started by NDLBox - Last post by FurryNutz
Sounds like a problem with the NVR and the one camera its changing. I recommend that you phone contact your regional D-Link support office and ask for help and information regarding this. We find that phone contact has better immediate results over using email.
Let us know how it goes please.

 7 
 on: September 23, 2017, 12:27:21 PM 
Started by NDLBox - Last post by Mr.Navy
Done - Unfortunately the symptom stays the same  :'(

Meanwhile I tested my DNS-320L with four (max.amount) cameras connected at Maximum Resolution:
- The DNS-320L does not "modify" the Settings - Therefore I do not see a bandwith Problem.

Possible that the bandwidth is getting maxed out having all that going on wifi.
Try this, turn off all other cameras and set the one camera for your desired profile and see if it's reset again after saving all the configurations.

 8 
 on: September 23, 2017, 12:06:33 PM 
Started by NDLBox - Last post by FurryNutz
Possible that the bandwidth is getting maxed out having all that going on wifi.
Try this, turn off all other cameras and set the one camera for your desired profile and see if it's reset again after saving all the configurations.

 9 
 on: September 23, 2017, 11:02:48 AM 
Started by NDLBox - Last post by Mr.Navy
1. I have Hardware Revision A
2. Firmware is the latest 2.40 / Device Pack 2.0.25
3. Installed Cameras are: 3x DCS-935L, 1x932L, 1x942L, 1x5010L (All with latest Firmware)
4. Six Camera installed in total
5. The router is from BT (Smart Hub)
6. WiFi is set to 2.4GHz N Standard
7. Beside the cameras is a notebook + Smartphone connected.
Link>Welcome!

  • What Hardware version is your DNR? Look at the sticker behind or under the device.
  • Link>What Firmware version is currently loaded? Found on the DNRs web page under status.
What model cameras are you using?
How many cameras are you using at once?

What Mfr and model main host wifi router are you using?
What wireless modes are you using?
What other wifi devices are connected along with the cameras to the main host router?

I am facing the same Problem - Since this Threat is quite old I hope that a solution is available?

same problem here with newest Firmware DLINK_DNR-326.2.40b04(2.40.0929.2015)(BETA) on a DNR-326 !
It seems that this bug is on all DNR's
all cams which are not connected to the DNR still works fine while changing settings for video profile 2 or 3, only cams connected to the DNR makes the changes, then a few seconds later the DNR set's the settings back to lower resolution and other codec and resets the cam.

my cams:
DCS-2210
DCS-5222LB1
DCS-7513
DCS-2332L

for me, it happens on all cams connected to DNR!

 10 
 on: September 23, 2017, 06:41:50 AM 
Started by lorx - Last post by PacketTracer
Hi,

please check if you have configured the D-Link Voice VLAN feature as described here, while adapting the sample situation to your needs.

The D-Link working model for voice vlan is to require the phone to send untagged frames that are dynamically assigned to the voice vlan according to the MAC source address of the phone (its OUI part, that is the first 24 bits which tell the vendor). I read somewhere that Cisco phones may also operate in a different way where they require CDP (Cisco Discovery Protocol) and a switch sending CDP (that is: a Cisco switch) in order to learn which voice vlan is configured by the switch and then send voice frames already tagged with that dynamically learned voice vlan ID. This operating mode wouldn't be compatible with a D-Link switch.

I don't know Fortigate, but according to my understanding of your scenario there are no compatibilty needs between D-Link's voice vlan features and your Fortigate: All you need is a VLAN trunk for voice and data vlan on the physical link between your D-Link switch and your Fortigate. In addition you need two DHCP scopes defining two IP pools for the different IP networks that are assigned to your data and voice vlan. Did you check if devices in data and voice vlan get IP addresses from the corresponding data and voice IP pool respectively? If your phones get IP addresses from the IP pool defined for your data vlan something goes wrong either with your DHCP and vlan configuration at the Fortigate side or with the correct vlan assignment of data (DHCP discover and request packets) sent from your phones to the switch.

PT

Pages: [1] 2 3 ... 10