DSM-G600, DNS-3xx and NSA-220 Hack Forum

Unfortunately no one can be told what fun_plug is - you have to see it for yourself.

You are not logged in.

Announcement

#1 2009-02-17 19:22:07

roxor
Member
Registered: 2009-02-17
Posts: 5

Cannot map drive on server2003

Hi folks,

Recently I have upgraded from firmware v1.03 to v1.06. I have domain (AD) with domain netbios name which I have set up on dns-323 workgroup too. Domain computers has no problem accessing \\Dlink\Volume_1 without prompt for username/psw. (it doesn't matter if it is vista/xp/server2003).On nas is only all permission set for folder volume_1. But strange thing that happend, I have one server 2003, which is not domain member, it's only in workgroup. On this server I was running backups of dlink files. After upgrade to 1.06 I cannot map a drive to nas anymore. "the network path specified does not exist". I have tryed all tips from http://dns323.kood.org/information:known_issues with no luck. I cannot map drive using net share and directly using "map network drive". I have tryed to create username with psw and group on dns-323. From my computer which is connected via VPN to company network (windows vista) I am able to see files in nas on both folders volume_1 and volume_1-1 using existing group\username and psw.

One more strange thing, I have tryed to use on server 2003 D-link easy search utlility and map drive with NO PROBLEM !!! But I'm not able to do that thing using net share command. Via utility I'm able to connect without username/psw directly to the Volume_1 too. But after closing terminal session the mapped drive is no longer accessible and my backups fails.

Offline

 

#2 2009-02-17 23:12:36

bq041
Member
From: USA
Registered: 2008-03-19
Posts: 709

Re: Cannot map drive on server2003

Can you access it from the server 2003 machine via the ip address?  Have you made an entry in the hosts and lmhosts files for the DNS323 (on the windows server 2003)?  If not, make an entry into those files for the DNS's ip address, as it could be a domain name issue.


DNS-323     F/W: 1.04b84  H/W: A1  ffp: 0.5  Drives: 2X 400 GB Seagate SATA-300
DNS-323     F/W: 1.05b28  H/W: B1  ffp: 0.5  Drives: 2X 1 TB  WD SATA-300
DSM-G600   F/W: 1.02       H/W: B                Drive:  500 GB WD ATA

Offline

 

#3 2009-02-18 20:54:50

roxor
Member
Registered: 2009-02-17
Posts: 5

Re: Cannot map drive on server2003

bq041 wrote:

Can you access it from the server 2003 machine via the ip address?  Have you made an entry in the hosts and lmhosts files for the DNS323 (on the windows server 2003)?  If not, make an entry into those files for the DNS's ip address, as it could be a domain name issue.

- Can you access it from the server 2003 machine via the ip address?

Of course, with the same result.

- Have you made an entry in the hosts and lmhosts files for the DNS323 (on the windows server 2003)? 

This is not necessary, because in my domain enviroment works perfect DNS server and the non-domain server 2003 works as backup DNS server for domain controller. I have only added new DNS record Host (A) Dlink with his IP address. It's the same if I ping "dlink" or "172.19.187.13", the ping response works perfect from Server 2003. I think that this is not that problem, I know very well how hosts works and name resolution in windows.

It's very strange that I can map network drive via Dlink Easy search utility, but can't do that via command or directly using map drive procedure.

After logoff and back logon the mapped drive is inacessible.

net use S: \\dlink\volume_1 or net use S: \\172.19.187.13\volume_1 I have also tryed>  net use S: \\dlink\volume_1-1 /user:backup backup

"backup" is an existing name and psw for dlink user for folder volume_1-1. I have also tryed expression using workgroup name, whose is user "backup" member on dns-323.

Example>

net use S: \\dlink\volume_1-1 /user:server07\backup backup  "server07" is name of workgroup and name of the nondomain server 2003.

Each time the result is:
System error 3 has occurred.

The system cannot find the path specified.

Offline

 

#4 2009-02-20 15:33:02

michaelscott
Member
Registered: 2009-02-20
Posts: 5

Re: Cannot map drive on server2003

When you click on Start, run, and type:

\\dlink\

Do you get a username and password dialog box or an error message?

Ditto with:

\\dlink\Volume_1\

Also, do a port scan from the 2003 box to dlink.  Try also clearing sessions (as you know how to:  net use * /d /y) and try your net use command again.

Lastly, can you ssh or telnet to the dlink server and diagnose from there?

Good luck,

MichaelScott

Offline

 

#5 2009-02-20 16:08:56

roxor
Member
Registered: 2009-02-17
Posts: 5

Re: Cannot map drive on server2003

michaelscott wrote:

When you click on Start, run, and type:

\\dlink\

Do you get a username and password dialog box or an error message?

Ditto with:

\\dlink\Volume_1\

Also, do a port scan from the 2003 box to dlink.  Try also clearing sessions (as you know how to:  net use * /d /y) and try your net use command again.

Lastly, can you ssh or telnet to the dlink server and diagnose from there?

Good luck,

MichaelScott

- When you click on Start, run, and type:

- \\dlink\

- Do you get a username and password dialog box or an error message?

No, just error msg:

"\\dlink" is not accesible. Perhaps you do not have the appropriate permission to access this item. Ask your server's administrator and verify your permissions.

- Ditto with:

-\\dlink\Volume_1\

Error msg: The path specified does not exist.

- Also, do a port scan from the 2003 box to dlink. 

Russian program Netview:

Port #:        Service:

80        http
110        pop3
139        netbios-ssn
443        https
445        microsoft-ds
3128        web proxy
8080       

- Try also clearing sessions (as you know how to:  net use * /d /y) and try your net use command again.

I have already tryed delete previous connections, and also server/dns323 restarts many times too.

- Lastly, can you ssh or telnet to the dlink server and diagnose from there?

no response, only web administration is available.

Offline

 

#6 2009-02-20 17:01:30

michaelscott
Member
Registered: 2009-02-20
Posts: 5

Re: Cannot map drive on server2003

Sorry things are getting crazy since the firmware update.

See if you can get wireshark or network monitor installed on w2k3 box and take it from there...

Obviously, we're trying to figure out what exactly it sends over the wire (what credentials it sends for authentication).

Maybe it is a "Internet Explorer Enhanced Security" issue or a DFS (replication?) issue.

Good luck,

MichaelScott

Offline

 

#7 2009-02-20 22:17:57

roxor
Member
Registered: 2009-02-17
Posts: 5

Re: Cannot map drive on server2003

michaelscott wrote:

Sorry things are getting crazy since the firmware update.

See if you can get wireshark or network monitor installed on w2k3 box and take it from there...

Obviously, we're trying to figure out what exactly it sends over the wire (what credentials it sends for authentication).

Maybe it is a "Internet Explorer Enhanced Security" issue or a DFS (replication?) issue.

Good luck,

MichaelScott

- See if you can get wireshark

So I have tryed your wireshark and started capturing communication between server and dns-323

I have send command : net use s: \\dlink\volume_1

the result of the capture is in attachment.


- Obviously, we're trying to figure out what exactly it sends over the wire (what credentials it sends for authentication).

- Maybe it is a "Internet Explorer Enhanced Security" issue or a DFS (replication?) issue.

Enhanced security is turned off (uninstalled from add/remove programs), because I hate stupid security when using explorer.

About DFS - I don't remember that I have installed or configured something like that.

I have found only Distributed File System service, which is set to start type manual and it's turned off. I don't use this feature.

Last edited by roxor (2009-02-20 22:31:13)


Attachments:
Attachment Icon 1.zip, Size: 2,839 bytes, Downloads: 157

Offline

 

#8 2009-02-22 21:51:12

roxor
Member
Registered: 2009-02-17
Posts: 5

Re: Cannot map drive on server2003

One more thing,

This error was happening with fmw 1.03 and also with 1.06 too.

My DNS-323 is model 1A.

With nas I bought two HDDs configured into RAID1.

type: Western Digital ST3500641AS.

The problem result from error when I turn the NAS on, the hdds aren't recognized. Two hdd's blue leds are blinking very intensively for a 10 or 15 seconds after then they stay blink slowly. When the system completely starts, there are no hdds in status page.

This thing only happens if I turn the nas on. The only way, how can I get hdds start working is system restart. After "software" restart system recognize disks and dns-323 works perfect.

Last edited by roxor (2009-02-22 22:09:53)

Offline

 

Board footer

Powered by PunBB
© Copyright 2002–2010 PunBB