Print

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

[ElmCityPinoy]

Hi all:

So I've trawled through all the Mapping threads I could find here and on Google and I'm still coming up short. Any help appreciated.

I have a DNS-321 with firmware 1.03 installed. My Windows 7 Netbook can map the drive just fine wirelessly - this tells me it's most likely not a firewall issue on the router or a wireless issue, but who knows?

My Windows XP SP3, however, comes up with "The Network is not present or not started" error when I try to access the DNS-321 from the Run command. And I get the error "The drive cannot be mapped because no network was found" when I try to map a drive.

Some more data points for you:

• All services are turned on (Workstation, Server, NetBIOS)
• Both Windows firewall and ESET NOD32 are disabled
• I can ping the DNS-321 from the XP machine
• I am able to print to a printer shared through another XP machine (I have not yet tried to access the NAS from this other XP machine - will do so tonight)
  

Thanks for your help!

ECP

[gunrunnerjohn]

Have you disabled ALL firewalls as a diagnostic aid?  Can you ping the DNS-321 by name, and not just by IP address?

[ElmCityPinoy]

Have you disabled ALL firewalls as a diagnostic aid?  Can you ping the DNS-321 by name, and not just by IP address?

Howdy. I have disabled all firewalls. And I can also ping the DNS-321 by name from the XP machine. No luck yet...

[gunrunnerjohn]

Can you share files using the problem machine that reside on other machines?

[ElmCityPinoy]

Can you share files using the problem machine that reside on other machines?

Interestingly enough, I cannot access other shares from the problem machine - I get the same error. But I can access files served from the problem machine on other computers in the network.

[gunrunnerjohn]

Now we're getting somewhere, this appears to simply be a Windows issue, nothing really to do with the NAS.

How about posting this.

Hold the Windows key and press R, then type CMD then press Enter to open a command prompt:

In the command prompt window that opens, type type the following commands, one at a time, followed by the Enter key:

Note that there is a space before the -n or the /ALL, but there is NOT a space after the - or / in the following commands.

NBTSTAT    -n

IPCONFIG /ALL

Right click in the command window and choose Select All, then hit Enter to copy the contents to the clipboard.
Paste the results in a message here.

If you are on a machine with no network connection, use a floppy, USB disk, or a CD-RW disk to transfer a text file with the information to allow pasting it here.

[ElmCityPinoy]

Sounds encouraging. Thanks, gunrunnerjohn!

Here's the output:


C:\DOCUME~1\TMRLAP~1>nbtstat -n

Wireless Network Connection:
Node IpAddress: [10.0.1.197] Scope Id: []

                NetBIOS Local Name Table

       Name               Type         Status
    ---------------------------------------------
    TMRLAPTOP      <20>  UNIQUE      Registered
    TMRLAPTOP      <00>  UNIQUE      Registered
    WORKGROUP      <00>  GROUP       Registered
    WORKGROUP      <1E>  GROUP       Registered

Local Area Connection:
Node IpAddress: [0.0.0.0] Scope Id: []

    No names in cache

C:\DOCUME~1\TMRLAP~1>ipconfig /all

Windows IP Configuration

        Host Name . . . . . . . . . . . . : TMRLAPTOP
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : gateway.2wire.net

Ethernet adapter Wireless Network Connection:

        Connection-specific DNS Suffix  . : gateway.2wire.net
        Description . . . . . . . . . . . : 11a/b/g Wireless LAN Mini PCI Express Adapter
        Physical Address. . . . . . . . . : 00-19-7D-FF-B9-80
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 10.0.1.197
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 10.0.1.1
        DHCP Server . . . . . . . . . . . : 10.0.1.1
        DNS Servers . . . . . . . . . . . : 10.0.1.1
        Lease Obtained. . . . . . . . . . : Friday, May 07, 2010 8:35:46 AM
        Lease Expires . . . . . . . . . . : Saturday, May 08, 2010 8:35:46 AM

Ethernet adapter Local Area Connection:

        Media State . . . . . . . . . . . : Media disconnected
        Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network Connection
        Physical Address. . . . . . . . . : 00-15-58-99-81-7C

C:\DOCUME~1\TMRLAP~1>

[gunrunnerjohn]

Can you post the same thing for the working machine that has no issues with the NAS access?

[ElmCityPinoy]

This is from a working XP SP3 machine that can map the NAS:


C:\DOCUME~1\OWNER>nbtstat -n

Local Area Connection:
Node IpAddress: [0.0.0.0] Scope Id: []

    No names in cache

Wireless Network Connection:
Node IpAddress: [10.0.1.187] Scope Id: []

                NetBIOS Local Name Table

       Name               Type         Status
    ---------------------------------------------
    TMROFFICE     <00>  UNIQUE      Registered
    TMROFFICE     <20>  UNIQUE      Registered
    WORKGROUP      <00>  GROUP       Registered
    WORKGROUP      <1E>  GROUP       Registered

\Device\NetBT_Tcpip_{C4762FF3-F4EB-4B9C-9425-90817DA503BE}:
Node IpAddress: [0.0.0.0] Scope Id: []

    No names in cache

C:\DOCUME~1\OWNER>ipconfig /all

Windows IP Configuration

        Host Name . . . . . . . . . . . . : tmroffice
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Broadcast
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : gateway.2wire.net

Ethernet adapter Local Area Connection:

        Media State . . . . . . . . . . . : Media disconnected
        Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
        Physical Address. . . . . . . . . : 00-15-F2-B5-7E-21

Ethernet adapter Wireless Network Connection:

        Connection-specific DNS Suffix  . : gateway.2wire.net
        Description . . . . . . . . . . . : D-Link Xtreme N
        Physical Address. . . . . . . . . : 00-1B-11-E8-72-A3
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 10.0.1.187
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 10.0.1.1
        DHCP Server . . . . . . . . . . . : 10.0.1.1
        DNS Servers . . . . . . . . . . . : 10.0.1.1
        Lease Obtained. . . . . . . . . . : Friday, May 07, 2010 9:26:16 AM
        Lease Expires . . . . . . . . . . : Saturday, May 08, 2010 9:26:16 AM

Ethernet adapter {C4762FF3-F4EB-4B9C-9425-90817DA503BE}:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Nortel IPSECSHM Adapter - Packet Scheduler Miniport
        Physical Address. . . . . . . . . : 44-45-53-00-54-42
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 0.0.0.0
        Subnet Mask . . . . . . . . . . . : 0.0.0.0
        Default Gateway . . . . . . . . . :

C:\DOCUME~1\OWNER>

[gunrunnerjohn]

Sure looks like a firewall issue to me.  One more thing to look at.  Compare the working and non-working computers.


Check that all your network services are Started:

• COM+ Event System (for WZC issues)
• Computer Browser
• DHCP Client
• DNS Client
• Network Connections
• Network Location Awareness
• Remote Procedure Call (RPC)
• Server
• TCP/IP Netbios helper
• Wireless  Zero Configuration ([COLOR="DarkRed"]XP wireless configurations only[/COLOR])
  
• WLAN AutoConfig ([COLOR="DarkRed"]Vista wireless configurations only[/COLOR])
  
• Workstation

Note: You can check the services in Control Panel, Administrative Tools, Services.

All of these services should be started, and their startup type should be automatic (or perhaps manual).

If a service is not running, open it's properties and check the dependencies.  Check each of the dependencies and see which one is preventing the service from running.  Checking the event log is also a good idea here, there may be clues to what is failing.

[ElmCityPinoy]

Thanks again so much for your help thus far, gunrunnerjohn.

I've verified that all services are running and I'm now looking into the various firewall(s) on my network. I have Windows Firewall and ESET NOD32 (although, not strictly a firewall) on the problem machine. When I disable both, I still get the same issue.

There is also a firewall on my router, a D-Link DIR-655 with v1.03 firmware.

Any hints as to what to look for in particular? I've reset the DIR-655 to factory defaults and have confirmed that my other machines still maintain access to the NAS but the problem machine does not.

[gunrunnerjohn]

The router firewall has no bearing here, that's only effective for the LAN <-> WAN interface.

Do you have any Internet Security applications running?  Clearly, something is affecting the file sharing.

You might also try a stack repair.

TCP/IP stack repair options for use with Windows XP with SP2/SP3.

   Start, Run, CMD to open a command prompt:

In the command prompt window that opens, type type the following commands, each followed by the Enter key:

Note: Type only the text in bold for the following commands.

Reset TCP/IP stack to installation defaults, type:  netsh int ip reset reset.log

Reset WINSOCK entries to installation defaults, type: netsh winsock reset catalog

Reboot the machine.

[ElmCityPinoy]

I've tried the TCP/IP stack repair to no effect.

AFAIK, the only Internet Security applications I have installed are Windows Firewall and ESET NOD32 Antivirus...

I'm beginning to think a rebuild may be in order.

[gunrunnerjohn]

I'm beginning to think you're right.

Have you booted in Safe Mode with Networking to see if that works?

[ElmCityPinoy]

Just tried Safe Mode with Networking and still no go. 

Any other last-ditch recommendations before I rebuild? Ugh, when it rains it pours I guess...