ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Solved Cant communicate

    IT Discussion
    network connection windows 7 windows xp networking
    12
    98
    8.7k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • dafyreD
      dafyre @WrCombs
      last edited by

      @wrcombs said in Cant communicate:

      @dafyre said in Cant communicate:

      Did you check the accounts on the Backoffice server?

      Guy on site is running window updates, apparently this pc has never been updated. He has control right now. Letting him do his thing.

      /me puts on a dang helmet. Good luck!

      WrCombsW 1 2 Replies Last reply Reply Quote 0
      • WrCombsW
        WrCombs @dafyre
        last edited by

        @dafyre said in Cant communicate:

        @wrcombs said in Cant communicate:

        @dafyre said in Cant communicate:

        Did you check the accounts on the Backoffice server?

        Guy on site is running window updates, apparently this pc has never been updated. He has control right now. Letting him do his thing.

        /me puts on a dang helmet. Good luck!

        LOL

        1 Reply Last reply Reply Quote 0
        • Emad RE
          Emad R @WrCombs
          last edited by Emad R

          @wrcombs

          Safe mode with network ? what happens ?

          What about try running the below before mount

          @REM delete all previous network drives#
          net use * /del /yes 
          
          @REM purge cached Kerberos authentication tickets#
          klist purge
          
          @REM newer way of automating the removal of all stored credentials.
          cmdkey.exe /list > "%TEMP%\List.txt"
          findstr.exe Target "%TEMP%\List.txt" > "%TEMP%\tokensonly.txt"
          FOR /F "tokens=1,2 delims= " %%G IN (%TEMP%\tokensonly.txt) DO cmdkey.exe /delete:%%H
          del "%TEMP%\List.txt" /s /f /q
          del "%TEMP%\tokensonly.txt" /s /f /q
          
          @REM killing explorer last step to prepare for the actual share mount
          taskkill /f /im explorer.exe & ping 127.0.0.1 -n 3 & start /im explorer.exe
          1 Reply Last reply Reply Quote 0
          • WrCombsW
            WrCombs @1337
            last edited by

            @pete-s said in Cant communicate:

            @wrcombs said in Cant communicate:

            0_1528219523696_chicken coop.PNG

            So it's the BOOTDRV share that the terminals connect to?

            yes

            So connecting to the back office server (with the right username replaced below) what was the response?

              net use \\192.168.128.xxx\BOOTDRV /user:username
            
            1 Reply Last reply Reply Quote 0
            • 1
              1337 @dafyre
              last edited by

              @dafyre said in Cant communicate:

              @wrcombs said in Cant communicate:

              @dafyre said in Cant communicate:

              Did you check the accounts on the Backoffice server?

              Guy on site is running window updates, apparently this pc has never been updated. He has control right now. Letting him do his thing.

              /me puts on a dang helmet. Good luck!

              Well, lets check back in a couple of hours. Actually windows will reset some settings when you install some updates.

              WrCombsW 1 Reply Last reply Reply Quote 0
              • WrCombsW
                WrCombs @1337
                last edited by

                @pete-s said in Cant communicate:

                @dafyre said in Cant communicate:

                @wrcombs said in Cant communicate:

                @dafyre said in Cant communicate:

                Did you check the accounts on the Backoffice server?

                Guy on site is running window updates, apparently this pc has never been updated. He has control right now. Letting him do his thing.

                /me puts on a dang helmet. Good luck!

                Well, lets check back in a couple of hours. Actually windows will reset some settings when you install some updates.

                Sounds like a plan.

                1 1 Reply Last reply Reply Quote 0
                • 1
                  1337 @WrCombs
                  last edited by 1337

                  @wrcombs said in Cant communicate:

                  @pete-s said in Cant communicate:

                  @dafyre said in Cant communicate:

                  @wrcombs said in Cant communicate:

                  @dafyre said in Cant communicate:

                  Did you check the accounts on the Backoffice server?

                  Guy on site is running window updates, apparently this pc has never been updated. He has control right now. Letting him do his thing.

                  /me puts on a dang helmet. Good luck!

                  Well, lets check back in a couple of hours. Actually windows will reset some settings when you install some updates.

                  Sounds like a plan.

                  Some of the next steps to troubleshoot are:

                  • open the share on the back office server from the back office server itself (this eliminates the network outside the machine)
                  • if above doesn't work check that the "File and Printer sharing from Microsoft Networks"-setting is enabled on the LAN interface properties.
                  • install and run a portscanner from one terminal to see that the ports are actually open over the network.
                  1 Reply Last reply Reply Quote 0
                  • ObsolesceO
                    Obsolesce
                    last edited by

                    Didn't read al 65 posts above, so may have been mentioned or I may have missed something....

                    But is 802.1x being used?

                    WrCombsW 1 Reply Last reply Reply Quote 0
                    • WrCombsW
                      WrCombs @Obsolesce
                      last edited by

                      @obsolesce said in Cant communicate:

                      Didn't read al 65 posts above, so may have been mentioned or I may have missed something....

                      But is 802.1x being used?

                      802.1x ? What is that and why would it be used?

                      IEEE 802.1X is an IEEE Standard for port-based Network Access Control (PNAC). It is part of the IEEE 802.1 group of networking protocols. It provides an authentication mechanism to devices wishing to attach to a LAN or WLAN. This is what i get when i google 802.1x
                      Is this what youre talking about?

                      ObsolesceO 1 Reply Last reply Reply Quote 0
                      • ObsolesceO
                        Obsolesce @WrCombs
                        last edited by

                        @wrcombs said in Cant communicate:

                        @obsolesce said in Cant communicate:

                        Didn't read al 65 posts above, so may have been mentioned or I may have missed something....

                        But is 802.1x being used?

                        802.1x ? What is that and why would it be used?

                        IEEE 802.1X is an IEEE Standard for port-based Network Access Control (PNAC). It is part of the IEEE 802.1 group of networking protocols. It provides an authentication mechanism to devices wishing to attach to a LAN or WLAN. This is what i get when i google 802.1x
                        Is this what youre talking about?

                        Yes

                        WrCombsW 1 Reply Last reply Reply Quote 0
                        • WrCombsW
                          WrCombs @Obsolesce
                          last edited by

                          @obsolesce said in Cant communicate:

                          @wrcombs said in Cant communicate:

                          @obsolesce said in Cant communicate:

                          Didn't read al 65 posts above, so may have been mentioned or I may have missed something....

                          But is 802.1x being used?

                          802.1x ? What is that and why would it be used?

                          IEEE 802.1X is an IEEE Standard for port-based Network Access Control (PNAC). It is part of the IEEE 802.1 group of networking protocols. It provides an authentication mechanism to devices wishing to attach to a LAN or WLAN. This is what i get when i google 802.1x
                          Is this what youre talking about?

                          Yes

                          This is the first time im ever hearing of this so im sure the answer to that is no

                          1 Reply Last reply Reply Quote 0
                          • KellyK
                            Kelly
                            last edited by

                            I'm facing a parallel issue where a workgroup share is inaccessible, so I've been doing a lot of testing. One of things I've noticed in my tests is that when the Windows Firewall is off then port 445 closes automatically. Have you tried it with the firewalls on, but with SMB-In configured properly in the firewall settings?

                            WrCombsW KellyK 2 Replies Last reply Reply Quote 0
                            • WrCombsW
                              WrCombs @Kelly
                              last edited by

                              @kelly said in Cant communicate:

                              I'm facing a parallel issue where a workgroup share is inaccessible, so I've been doing a lot of testing. One of things I've noticed in my tests is that when the Windows Firewall is off then port 445 closes automatically. Have you tried it with the firewalls on, but with SMB-In configured properly in the firewall settings?

                              I have not..

                              1 Reply Last reply Reply Quote 0
                              • KellyK
                                Kelly @Kelly
                                last edited by

                                You can test the port using telnet or ssh (assuming you have either installed on a client). It will at least tell you if you can reach the port.

                                WrCombsW 1 Reply Last reply Reply Quote 1
                                • WrCombsW
                                  WrCombs @Kelly
                                  last edited by

                                  @kelly said in Cant communicate:

                                  You can test the port using telnet or ssh (assuming you have either installed on a client). It will at least tell you if you can reach the port.

                                  I dont believe i have either installed on the client side

                                  KellyK 1 Reply Last reply Reply Quote 0
                                  • KellyK
                                    Kelly @WrCombs
                                    last edited by

                                    @wrcombs said in Cant communicate:

                                    @kelly said in Cant communicate:

                                    You can test the port using telnet or ssh (assuming you have either installed on a client). It will at least tell you if you can reach the port.

                                    I dont believe i have either installed on the client side

                                    https://chocolatey.org/packages/openssh

                                    1 1 Reply Last reply Reply Quote 0
                                    • 1
                                      1337 @Kelly
                                      last edited by

                                      @kelly said in Cant communicate:

                                      @wrcombs said in Cant communicate:

                                      @kelly said in Cant communicate:

                                      You can test the port using telnet or ssh (assuming you have either installed on a client). It will at least tell you if you can reach the port.

                                      I dont believe i have either installed on the client side

                                      https://chocolatey.org/packages/openssh

                                      Better to use a port scanner, for instance nmap for windows. https://nmap.org/download.html

                                      KellyK 1 Reply Last reply Reply Quote 0
                                      • KellyK
                                        Kelly @1337
                                        last edited by

                                        @pete-s said in Cant communicate:

                                        @kelly said in Cant communicate:

                                        @wrcombs said in Cant communicate:

                                        @kelly said in Cant communicate:

                                        You can test the port using telnet or ssh (assuming you have either installed on a client). It will at least tell you if you can reach the port.

                                        I dont believe i have either installed on the client side

                                        https://chocolatey.org/packages/openssh

                                        Better to use a port scanner, for instance nmap for windows. https://nmap.org/download.html

                                        I would use Nmap on my system, but for troubleshooting a client machine I'd rather use something lighter and faster. YMMV

                                        1 1 Reply Last reply Reply Quote 0
                                        • 1
                                          1337 @Kelly
                                          last edited by

                                          @kelly said in Cant communicate:

                                          @pete-s said in Cant communicate:

                                          @kelly said in Cant communicate:

                                          @wrcombs said in Cant communicate:

                                          @kelly said in Cant communicate:

                                          You can test the port using telnet or ssh (assuming you have either installed on a client). It will at least tell you if you can reach the port.

                                          I dont believe i have either installed on the client side

                                          https://chocolatey.org/packages/openssh

                                          Better to use a port scanner, for instance nmap for windows. https://nmap.org/download.html

                                          I would use Nmap on my system, but for troubleshooting a client machine I'd rather use something lighter and faster. YMMV

                                          Yes, but installing the complete openssh server on windows isn't light weight.
                                          For telnet and ssh client it's better to just run putty.exe in that case.
                                          https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html

                                          KellyK 1 Reply Last reply Reply Quote 0
                                          • KellyK
                                            Kelly @1337
                                            last edited by

                                            @pete-s said in Cant communicate:

                                            @kelly said in Cant communicate:

                                            @pete-s said in Cant communicate:

                                            @kelly said in Cant communicate:

                                            @wrcombs said in Cant communicate:

                                            @kelly said in Cant communicate:

                                            You can test the port using telnet or ssh (assuming you have either installed on a client). It will at least tell you if you can reach the port.

                                            I dont believe i have either installed on the client side

                                            https://chocolatey.org/packages/openssh

                                            Better to use a port scanner, for instance nmap for windows. https://nmap.org/download.html

                                            I would use Nmap on my system, but for troubleshooting a client machine I'd rather use something lighter and faster. YMMV

                                            Yes, but installing the complete openssh server on windows isn't light weight.
                                            For telnet and ssh client it's better to just run putty.exe in that case.
                                            https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html

                                            Putty used to have less than helpful error messages. It looks like that has changed since the last time I used it. Either way, I'm done arguing with you.

                                            1 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 5
                                            • 4 / 5
                                            • First post
                                              Last post