none
Windows 7 64-bit Home Premium cant access Windows 2003 server shared folder

    Question

  • I have been through countless forums looking at a ton of information. The easiest way is to breakdown exactly everything I tried and failed to work.

    1. File sharing is enabled everywhere known to man. Network connection file and print sharing is selected, simple file sharing in the folder options is on.

    2. NetBIOS is active,started,enabled in Network connections and in services.msc

    3. IPv6 has been disabled on my network connection

    4. Used the following reg file.

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
    "LmCompatibilityLevel"=dword:00000001

    5. Everybody is on the same Workgroup

    6.There are no domains, no users, no printers,no nothing set-up on the Windows 2003 server where there is a D: drive that has a shared folder that allows access to by everyone.

    7. Ran the following lines of code as administrator cmd.exe found in one forum

    netsh winsock reset
    netsh int ip reset c:\temp\resetlog.txt

    8. I can ping the server by IP but not by name.

    9. When I try to connect to the server that I see is in my Workgroup I get error 0x8007035 which just says I cant find it.

    10. I added the server \\servername in the trusted sites in my internet explorer just for fun.

    11. Our office has static ips which makes it easier to problem solve but will eventually get DHCP rolling.

    12. I can get the logon screen for the server in Windows XP but not in Windows Vista or 7 running 32-bit or 64-bit. I can see it, ping it but connection to the file path doesnt exist.

    13. I dont have 200 Microsoft 6to4 adapters in my device manager. Only have 1.

    14. I have Windows 7 Home Premium so i cant use gpedit.msc or serpol.msc to edit any policies I saw through multiple forums worked for this particular issue.

    15. The server is on a 1 Gigbit switch port on the same subnet 255.255.255.0 as everyone else.

    16. No name or ip confilicts and the folder that is shared is not hidden. I have made sure everybody is in the permissions of the shared folder.

    17. I have turn the firewall completely off on windows and I dont have antivirus firewalls.

    18. I turned on network discovery and made sure all the other settings were good according to numerous other forums. Turn on  file and print sharing
    -Turn off password protected sharing
    -Use user accounts and passwords to connect to other computers

    19. I flushed my DNS

    ipconfig /flushdns 
     ipconfig /registerdns


    20. I tried to connect to it via \\ipaddress\sharedfolder

    21. I went to  "Local Policies" -> "Security Options".  Now look for the entry "Network Security: LAN Manager authentication level" and open it.  Click on the dropdown menu and select "Send LM & NTLM - use NTLMv2 session security if negotiated".  Apply the settings.
     

    22. Change Regional settings Date Time & seconds to be the same as the server

    23. Disabled UAC

     

    That is everything I have done to this point I believe. I may forgot a step or two but as you can tell it lists pretty much everything I could find.

     

    Friday, September 09, 2011 8:50 PM

All replies

  • Hi,

    the point 8 - if  you can ping the server by IP but not by name, then when you try to connect to the server that you see in your Workgroup you get error 0x8007035 which just says it can not find it, because your computer is unable to resolve the host (server) name into IP address.

    You can add the new line in the file "hosts" (it is the text file) stored in the directory "c:\windows\system32\drivers\etc":

    ip_address    name_of_server

    after adding the new line, save the file (no need to restart), try the command "ping name_of_server" and try to connect to the server that you see in your Workgroup.

    What about the point 20 ( I tried to connect to it via \\ipaddress\sharedfolder) - did you get any error message ?


    LC
    Sunday, September 11, 2011 6:47 PM
  • As you can see in the following screenshot the hosts trick worked with the domain name resolution however when I connect to  the server using my XP Professional computer I still get the issue where it says network path can not be found.

    With point 20 it still gave me the same issue that says \\ip_address\sharedfolder the network path could not be found. On my XP Professional computer I did try editing the group and local policies without any success. Its odd becuase 5/15 computers can connect without any issue running XP 3/15 that have XP have issues connecting and the other various 7 and Vista clients all have issues connecting to the Windows 2003 server. I have been trying to go value by value trying to figure out what could be the difference in the computers.

    Defianetly aggrevating... We have a Windows Server 2000 that everyone connects to but is too small to handle all the data thus we are moving to a larger server with 2003, what the company bought a while ago but hasnt utilized. I am just trying to something simplistic to start with but has been nothing but odd issues with connectivity.

    Monday, September 12, 2011 12:54 PM
  • Only quick question - when you try to click "Start" - "Run" and write only "\\ip_address" and click "OK". Do you get the same error message - "path not found" ? (ip_address = ip address of Windows server 2003)
    LC
    Monday, September 12, 2011 3:16 PM
  • LC,

    Yes you are correct even if I do \\ip_address it still gives me the same error thus is why im trying all these other methods to get connectivity. It seems like there must be something wrong with the set-up on the individual machines if I can connect with some and not with others even though they have the same OS.

    Monday, September 12, 2011 4:14 PM
  • Did you (or Can you) try to run "Safe Mode with networking" and try click "Start" - "Run" and write only "\\ip_address" and click "OK" - same error message?

    http://windows.microsoft.com/en-US/windows7/Start-your-computer-in-safe-mode

    part:

    Advanced Boot Options


    LC
    Tuesday, September 13, 2011 9:18 AM
  • LC,

    No I didnt try that yet, however once I did I got the error "No Network provider accepted the given network path"

    So I googled around and found some proposed solutions im working through now using sfc /scannow function to restore windows protected files making sure the windows files are intact and it the original files.

    If you have anything else you would like to suggest in the meantime please do so.

    Tuesday, September 13, 2011 1:00 PM
  • Dragonruler12,

    I think you found this article: http://support.microsoft.com/kb/841570/en

    So next what you can try - test the open ports by Portqry.exe command-line utility from station to the server.

    The following ports are associated with file sharing and server message block (SMB) communications:
    Microsoft file sharing SMB: User Datagram Protocol (UDP) ports from 135 through 139 and Transmission Control Protocol (TCP) ports from 135 through 139.
    Direct-hosted SMB traffic without a network basic input/output system (NetBIOS): port 445 (TCP and UPD).
    Source:

     Here is the description (and download) of the Portqry.exe command-line utility: http://support.microsoft.com/kb/310099/en

     


    LC
    Tuesday, September 13, 2011 8:00 PM
  • Ok LC,

    I downloaded and installed the utility to my path C:\WINDOWS\system32 folder to run in command line.

    While trying UDP protocol first I got the following:

    PortQry Version 2.0 Log File

    System Date: Wed Sep 14 08:33:22 2011

    Command run:
     portqry -n 10.1.10.5 -p udp -o 135,136,138,139,137 -l udp_135139.txt

    Local computer name:

     ENVISION-2E9BB2

    Querying target system called:

     10.1.10.5

    Attempting to resolve IP address to a name...


    IP address resolved to ECLAdmin

    querying...

    UDP port 135 (epmap service): LISTENING or FILTERED

    Using ephemeral source port
    Querying Endpoint Mapper Database...
    Server's response:

    RPC Endpoint Mapper did not respond

    UDP port 135 is FILTERED


    UDP port 136 (unknown service): LISTENING or FILTERED

    UDP port 138 (netbios-dgm service): LISTENING or FILTERED

    UDP port 139 (unknown service): LISTENING or FILTERED

    UDP port 137 (netbios-ns service): LISTENING or FILTERED

    Using ephemeral source port
    Attempting NETBIOS adapter status query to UDP port 137...

    Adapter status query failed.
    UDP port: FILTERED

     

    ========= end of log file =========

      PortQry developed by Tim Rains

    I also got the following error message when trying UDP port 137..

    Im not sure what in the world that means is it a environmental variable..becuase I dont see it on the list of environmental variables. So im guessing its something in the program looking for something in particular.

    Next I tried TCP on the same ports this is what I got:

    PortQry Version 2.0 Log File

    System Date: Wed Sep 14 08:42:06 2011

    Command run:
     portqry -n 10.1.10.5 -p tcp -r 135:139 -l tcp_135139.txt

    Local computer name:

     ENVISION-2E9BB2

    Querying target system called:

     10.1.10.5

    Attempting to resolve IP address to a name...


    IP address resolved to ECLAdmin

    querying...

    TCP port 135 (epmap service): FILTERED

    TCP port 136 (unknown service): FILTERED

    TCP port 137 (netbios-ns service): FILTERED

    TCP port 138 (unknown service): FILTERED

    TCP port 139 (netbios-ssn service): FILTERED


    ========= end of log file =========

      PortQry developed by Tim Rains

    Next I tried the last port you suggest 445 using both TCP and UDP with the same result...

    PortQry Version 2.0 Log File

    System Date: Wed Sep 14 08:54:58 2011

    Command run:
     portqry -n 10.1.10.5 -p udp -o 445 -l SMTP.txt

    Local computer name:

     ENVISION-2E9BB2

    Querying target system called:

     10.1.10.5

    Attempting to resolve IP address to a name...


    IP address resolved to ECLAdmin

    querying...

    UDP port 445 (microsoft-ds service): LISTENING or FILTERED

    TCP port 445 (microsoft-ds service): FILTERED


    ========= end of log file =========

      PortQry developed by Tim Rains

    If you need me to test more ports let me know...It seems like something is wrong becuase nothing is working. I am not sure if this means its a server issue than a station issue becuase it doesnt seem that the server is listening or if it is, the ports are strickly filtered.

    Thanks for the help so far...


    Wednesday, September 14, 2011 12:58 PM
  • OK, yes something is wrong, UDP ports are maybe OK, but TCP should looks like this:

    TCP port 135 (epmap service): LISTENING
    TCP port 136 (unknown service): FILTERED
    TCP port 137 (netbios-ns service): FILTERED
    TCP port 138 (unknown service): FILTERED
    TCP port 139 (netbios-ssn service): LISTENING
    TCP port 445 (microsoft-ds service): LISTENING

    I ran the command prompt as administrator (elevated) and I use this command :
    portqry -n 192.168.0.4 -p tcp -r 135:139 -l server_135_139_tcp.txt
    portqry -n 192.168.0.4 -p udp -r 135:139 -l server_135_139_udp.txt
    and all ran without the errors.

    How to run command prompt as Administrator (Elevated) is here:
    part:
    How do I run a command with elevated privileges?
    http://windows.microsoft.com/en-US/windows7/Command-Prompt-frequently-asked-questions

     

    I think you do not use the own DNS server on Server 2003, do you ? and you use the DNS from your ISP?

    Next - download the very useful program TCPView from Sysinternals:
    http://technet.microsoft.com/en-us/sysinternals/bb897437

    Unzip the program and run it on the server. Pres CTRL + R to disable the resolving and sort by the column Local port . You should see something like this (the important column Local port ans State):
    https://skydrive.live.com/#!/?cid=23fd66efd8d06b76&sc=photos&uc=1&id=23FD66EFD8D06B76%21113!cid=23FD66EFD8D06B76&id=23FD66EFD8D06B76%21163&sc=photos

    Do you see "Listening" on the line with ports 445,139 and 135 ?
    Do you have some another client computer? Does it have the same problem with connecting to the server?


    LC



    Wednesday, September 14, 2011 9:43 PM
  • ok well i have ran the TCPView on the server and on the computer that can connect to the ECLAdmin server.

    Server sorted by Local Ports

    TCPView Server sorted by State

    IdaDesktop that is connected to ECLAdmin, Has windows xp sp3 OS just like the one im having issues with...

     


    Thursday, September 15, 2011 5:22 PM
  •  

    I am connect and can see the Admin shared folder. Didnt have to use no ip tricks with the host file and connect via name.

    This is the computer I am trying to compare this one im writing the message with. No clue whats the difference..

    On the server here is the DNS im using which is the ISP.

    This is the same DNS all the computers in the office have. I didnt set up nothing except a shared folder on the server.

    So I know some work some dont work in the office however we have 1 40 port switch that everyone is connected to then that goes to the server. Everyone has the exact same network setup.

    Thursday, September 15, 2011 5:25 PM
  • OK,

    the communication between the server and the station with windows XP works OK. You can test the program PortQry - run the program on the Windows XP and test the connection to the server - the result should be the same as mine.

    You forgot to turn off the translation of numbers to names - would be better to see the port numbers (as I have on the picture, but it does not matter)

    Because you do not use own DNS server and do not use WINS server, so the translation of computer name to the IP address is done using Netbios. Netbios works on the port 139 (netbios-ssn) and use broadcasting. And because the communication between the server and the station with windows XP through port 139 works OK, then you didnt have to use ip tricks with the host file and you could connect via name.

    Note - Windows Vista and higher , Windows server 2008 and higher use LLMNR (Link Local Multicast Name Resolution) for the translating but only if there is no lower OS (Windows XP and lower, Windows server 2003 and lower) - if there is one of them on the network, then have to use Netbios too.

     We can do a small test - you use one 40-ports switch - can you swap the cables in the switch ? - I think the cable from WIN XP connects to the port of WINDOWS 7 and the cable from WINDOWS 7 connects to the port of WIN XP ? - just to be sure that we eliminate some error of the switch (or any setting if the switch is with management) - still works WIN XP connection after swapping ?

    Can you send me the result of command "ipconfig /all" (without quotes) running on the Windows 7 - write this command in command prompt.
    How to run command prompt as Administrator (Elevated) is here:
    http://windows.microsoft.com/en-US/windows7/Command-Prompt-frequently-asked-questions

    part:
    How do I run a command with elevated privileges?
    The result of the command COPY and PASTE here.

    And own sharing files and printers use port 445 (microsoft-ds) - and how you can see, that works OK on the server and the station with Windows XP

    Summary:
    1) test the program PortQry - run the program on the Windows XP do the test to the server
    2) swap cables on the switch (between WIN 7 an WIN XP) and test connection to the server (if it is possible)
    3)  COPY and PASTE here ipconfig /all from WIndows 7


    LC
    Thursday, September 15, 2011 10:30 PM
  • Well I have done what you said to do for "1) test the program PortQry - run the program on the Windows XP do the test to the server"

    I got the error where it couldnt resolve the IP to a name or the name to a ip. I did net view command and i saw

    \\ECLServer   <- Microsoft server 2000

    \\Idadesktop  <- Currently using that can connect to the ECLAdmin server

    \\ECLAdmin      Ecladmin     <- Microsoft Server 2003


    So i used Portqry for the 10.1.10.2 (ECLServer) and got the following....

    PortQry Version 2.0 Log File

    System Date: Fri Sep 16 10:53:22 2011

    Command run:
     portqry -n 10.1.10.2 -p tcp -r 135:139 -l tcp_135139.txt

    Local computer name:

     IDADESKTOP

    Querying target system called:

     10.1.10.2

    Attempting to resolve IP address to a name...


    IP address resolved to ECLSERVER

    querying...

    TCP port 135 (epmap service): LISTENING

    TCP port 136 (unknown service): NOT LISTENING

    TCP port 137 (netbios-ns service): NOT LISTENING

    TCP port 138 (unknown service): NOT LISTENING

    TCP port 139 (netbios-ssn service): LISTENING


    ========= end of log file =========

      PortQry developed by Tim Rains

    and...

    PortQry Version 2.0 Log File

    System Date: Fri Sep 16 10:52:51 2011

    Command run:
     portqry -n 10.1.10.2 -p udp -r 135:139 -l udk_135139.txt

    Local computer name:

     IDADESKTOP

    Querying target system called:

     10.1.10.2

    Attempting to resolve IP address to a name...


    IP address resolved to ECLSERVER

    querying...

    UDP port 135 (epmap service): NOT LISTENING

    UDP port 136 (unknown service): NOT LISTENING

    UDP port 137 (netbios-ns service): LISTENING or FILTERED

    Using ephemeral source port
    Attempting NETBIOS adapter status query to UDP port 137...

    Server's response: MAC address 00065bf2b375
    UDP port: LISTENING

    UDP port 138 (netbios-dgm service): LISTENING or FILTERED

    UDP port 139 (unknown service): NOT LISTENING


    ========= end of log file =========

      PortQry developed by Tim Rains

     

    So I am guessing I need something that looks like the above for the ECLAdmin server.

     

    Then I tried your work around for the ip name issue using the hosts file adding the ECLAdmin name and ip to the list...there seems something wrong with the netbios then where it can resolve the name of the ECLAdmin server.

    I got the following:

    PortQry Version 2.0 Log File

    System Date: Fri Sep 16 10:56:35 2011

    Command run:
     portqry -n ECLAdmin -p tcp -r 135:139 -l tcp_135139.txt

    Local computer name:

     IDADESKTOP

    Querying target system called:

     ECLAdmin

    Attempting to resolve name to IP address...


    Name resolved to 10.1.10.5

    querying...

    TCP port 135 (epmap service): FILTERED

    TCP port 136 (unknown service): FILTERED

    TCP port 137 (netbios-ns service): FILTERED

    TCP port 138 (unknown service): FILTERED

    TCP port 139 (netbios-ssn service): FILTERED


    ========= end of log file =========

      PortQry developed by Tim Rains

    and for UDP

    PortQry Version 2.0 Log File

    System Date: Fri Sep 16 10:55:58 2011

    Command run:
     portqry -n ECLAdmin -p udp -r 135:139 -l udk_135139.txt

    Local computer name:

     IDADESKTOP

    Querying target system called:

     ECLAdmin

    Attempting to resolve name to IP address...


    Name resolved to 10.1.10.5

    querying...

    UDP port 135 (epmap service): LISTENING or FILTERED

    UDP port 136 (unknown service): LISTENING or FILTERED

    UDP port 137 (netbios-ns service): LISTENING or FILTERED

    Using ephemeral source port
    Attempting NETBIOS adapter status query to UDP port 137...

    Adapter status query failed.
    UDP port: FILTERED


    UDP port 138 (netbios-dgm service): LISTENING or FILTERED

    UDP port 139 (unknown service): LISTENING or FILTERED


    ========= end of log file =========

      PortQry developed by Tim Rains

    So i did the Ipconfig /all on this particular computer that can connect to the ECLAdmin shared folder to show you their setting. I will get back to you on the windows 7 one.

    Windows IP Configuration



            Host Name . . . . . . . . . . . . : idadesktop

            Primary Dns Suffix  . . . . . . . :

            Node Type . . . . . . . . . . . . : Unknown

            IP Routing Enabled. . . . . . . . : No

            WINS Proxy Enabled. . . . . . . . : No



    Ethernet adapter Local Area Connection:



            Connection-specific DNS Suffix  . :

            Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controller

            Physical Address. . . . . . . . . : 00-1D-09-12-53-41

            Dhcp Enabled. . . . . . . . . . . : No

            IP Address. . . . . . . . . . . . : 10.1.10.42

            Subnet Mask . . . . . . . . . . . : 255.255.255.0

            Default Gateway . . . . . . . . . : 10.1.10.1

            DNS Servers . . . . . . . . . . . : 68.87.64.146

                                                         68.87.75.194

     

    Hopefully this helps. I will try to switch the two on the switch. Its unmanaged (that i know of) so it shouldnt matter. I believe its a netgear something. Specifications on the switch will be soon...

     

    Friday, September 16, 2011 3:02 PM
  • So I did the small picture of your network:
    https://skydrive.live.com/#!/?cid=23fd66efd8d06b76&sc=photos&uc=1&id=23FD66EFD8D06B76%21113!cid=23FD66EFD8D06B76&id=23FD66EFD8D06B76%21164&sc=photos

    1) Can you try to run PortQry from Windows XP to ECLAdmin port 445 TCP and UDP ?

    You tried to run only port 135..139, that were fitered and therefore the name ECLAdmin could not be resolved into ip address.

    But how can you see on my picture - the ports 139 and 135 have the state LISTENING - so maybe something have to block the netbios communication.

    2) Can you try to run ping from "idadesktop" to "ENVISION-2E9BB2" (I think it is name of WIN 7) and use the name instead of ip address (to check netbios working)

    ipconfig /all on WINXP looks good. We'll see how it will look like "ipconfig /all" on WIN 7.

    3) Can you try to run  TCPView from Sysinternals on WIN 7 (sort by STATE), to see what ports have the STATE "LISTENING"


    LC
    Saturday, September 17, 2011 9:06 PM
  • I like your picture however both idadesktop and ENVISION-2E9BB2 are windows xp service pack 3 OS. The following ADuca-HP computer has windows 7.

    Here is the ipconfig /all in administrator cmd

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : ADuca-HP
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
       Physical Address. . . . . . . . . : E0-69-95-96-A1-FC
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 10.1.10.26(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 10.1.10.1
       DNS Servers . . . . . . . . . . . : 68.87.64.146
                                                    68.87.75.192
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter VMware Network Adapter VMnet1:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
       Physical Address. . . . . . . . . : 00-50-56-C0-00-01
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::6ca4:5f81:825b:2caf%16(Preferred)
       Autoconfiguration IPv4 Address. . : 169.254.44.175(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 453005398
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-5F-39-98-E0-69-95-96-A1-FC
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter VMware Network Adapter VMnet8:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
       Physical Address. . . . . . . . . : 00-50-56-C0-00-08
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::f9aa:dc87:43cd:758a%17(Preferred)
       Autoconfiguration IPv4 Address. . : 169.254.117.138(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 469782614
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-5F-39-98-E0-69-95-96-A1-FC
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{45E3F5AB-7839-49EF-8DB9-02C5B67087FB}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 9:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft 6to4 Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 12:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{6905BC13-87C5-4C53-9F53-DF3B725E0698}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{5F822A5E-75FF-46E4-A3DD-91101B78DB0C}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Now I ran ping ENVISION-2E9BB2 from the command line on the windows 7 computer to windows xp and got

    Pinging ENVISION-2E9BB2 [10.1.10.156] with 32 bytes of data:
    Reply from 10.1.10.156: bytes=32 time<1ms TTL=128
    Reply from 10.1.10.156: bytes=32 time<1ms TTL=128
    Reply from 10.1.10.156: bytes=32 time<1ms TTL=128
    Reply from 10.1.10.156: bytes=32 time<1ms TTL=128

    Ping statistics for 10.1.10.156:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms

    I will get back to you on the idadesktop to envision/Aduca computers ping.

    I ran TCPView on the windows 7 machine i got the following listening ports by state. I did the Ctrl+R to show the local ports instead of names.

    Hopefully this is a step toward the right direction. I see listening on port 135 and 445 on windows 7 machine.

    Monday, September 19, 2011 12:56 PM
  • Ok now from idadesktop
    PortQry Version 2.0 Log File

    System Date: Mon Sep 19 15:42:37 2011

    Command run:
     portqry -n ECLAdmin -p udp -o 445 -l netbiosudp445.txt

    Local computer name:

     IDADESKTOP

    Querying target system called:

     ECLAdmin

    Attempting to resolve name to IP address...


    Name resolved to 10.1.10.5

    querying...

    UDP port 445 (microsoft-ds service): LISTENING or FILTERED


    ========= end of log file =========

      PortQry developed by Tim Rains

    and

    PortQry Version 2.0 Log File

    System Date: Mon Sep 19 15:42:57 2011

    Command run:
     portqry -n ECLAdmin -p tcp -o 445 -l netbiostcp445.txt

    Local computer name:

     IDADESKTOP

    Querying target system called:

     ECLAdmin

    Attempting to resolve name to IP address...


    Name resolved to 10.1.10.5

    querying...

    TCP port 445 (microsoft-ds service): FILTERED


    ========= end of log file =========

      PortQry developed by Tim Rains

    Its interesting that the TCP is filtered though from the server...

    I know on TCPView that it is set to listening which is odd... What do you think LC?

    I may just make my own partition on the server an get domains up and using our own DNS and active directory...

    Monday, September 19, 2011 7:49 PM
  • Yes, that is very interesting - if I understand it well - all ports (135,139,445) are filtered from IDADESKTOP to server ECLAdmin, but network sharing is working from IDADESKTOP to server ECLAdmin ?

    - modifed picture:
    https://skydrive.live.com/?cid=23FD66EFD8D06B76&id=23FD66EFD8D06B76%21165&sc=photos

    I have the MS Server 2008 standard (clean install - without DNS, DHCP, AD) and only what I did in settings, was - enable "File and Print sharing" in Firewall, which was disabled by default for PortQry working
    I had to set the Share permissions (Everyone to Full Control), NTFS premissions (Everyone to Full Control) and disable "Password protected sharing" for sharing folder .


    LC
    Monday, September 19, 2011 11:34 PM
  • Well LC I got my XP ENVISION computer to successfully connect to the ECLAdmin server by opening the port 445 through the firewall...I know on my local machines that it allows file and folder sharing through the firewall so I thought to allow it on the network connection on the ECLAdmin.

    I know not best practices however I can connect to it via ip on the windows 7 machines but not by name so the netbios issue is still occuring. I can deal with that issue becuase we need to transition between the ECLServer and ECLAdmin really soon becuase there is a lot more space on ECLAdmin and ECLServer is older than time. So I can at least connect everyone to the server for now and then start getting domains set-up and active directory on unallocated space on the server than do the major transition and see what issues arise then.

    So for now I guess this is solved since I got connectivity even though it isnt the best thing to do..it works for now.

    Wednesday, September 21, 2011 12:24 PM
  • OK, thank you for information. If you start getting domains set-up and active directory, you have to set-up DNS and this could resolve the problem with translation the name into ip address. DNS use port 53 TCP and UDP - both have to be enabled on the firewall. And you can test it through PortQry.

    Note - Windows Home Premium can not connect into domain controller - only Professional, Enterprise and Ultimate can.


    LC

    Wednesday, September 21, 2011 1:34 PM