Home / server / Questions / 58857
Accepted
mmcg
Asked: 2009-08-27 01:08:47 +0800 CST

Unable to connect to network share

  • 772

On our company network there are a number of clients that are having problems connecting to the company file server (Windows Server 2003 R2 Enterprise x86). The share are mapped to a drive letter on the client. The drives are showing up with a red X and can't be opened.

Most people can access the network shares ok.

I have an idea that the workstation service is at fault. The output of net config workstation on a faulty computer is 

C:\>net config workstation
Computer name                        \\vistacomputer
Full Computer name                   vistacomputer.xxxx.xxxx-xxxxxx.co.uk
User name                            username

Workstation active on 

Software version                     Windows Vista (TM) Business

Workstation domain                   xxxxxx
Workstation Domain DNS Name          xxxxxx.xxxx-xxxxxxxxx.co.uk
Logon domain                         xxxxxx

COM Open Timeout (sec)               0
COM Send Count (byte)                16
COM Send Timeout (msec)              250
The command completed successfully.

On a working computer it is

C:\>net config workstation
Computer name                        \\vistacomputerthatworks
Full Computer name                   vistacomputerthatworks.xxxx.xxxx-xxxxxx.co.uk
User name                            username

Workstation active on
     NetbiosSmb (000000000000)
     NetBT_Tcpip_{DABE06A7-5BF8-4ADF-B6C4-73EDB8D7971B} (00505694241B)

Software version                     Windows Vista (TM) Business

Workstation domain                   xxxxxx
Workstation Domain DNS Name          xxxxxx.xxxx-xxxxxxxxx.co.uk
Logon domain                         xxxxxx

COM Open Timeout (sec)               0
COM Send Count (byte)                16
COM Send Timeout (msec)              250
The command completed successfully.

Looks like the workstation service is disassociating itself from the network connections.

Any ideas?

networking

4 Answers

  1. OK, identify what's different about the clients that don't work. Software installed, patch levels, switch ports connected to, whatever.

    • 0

  2. This site seemed to hint (if you read the replies) that it's antivirus related or irpsize in the registry that's related to the issue you're describing.

    • 0

  3. First Check if the client is able to access other computer's shared folders or not. If not than try following.

    Sometimes because of some critical windows process, windows automatically stops following services.

    (1) Background Intelligent Transfer Services (2) Computer Browser (3) Network Connection

    Make Sure this services are running.

    Click Start > Run > Type Services.msc Click Enter to access service console.

    click on the service mentioned above. Right Click on it and click start.

    Hope this will work for you.

    • 0
  4. Best Answer

    I think I've solved this problem. It's some how related to IPv6. When I disable IPv6 on the problematic systems and then delete all the 6TO4 adapters then the workstation service comes back to life. I deleted all the adapters using devcon.exe from windows support tools. Hope this helps someone

    • 0