share problems




I offer this in hopes it may help someone else. I had two problems, I could not add computers to the domain and I could not access a shared folder on a Windows 2008 Server from Vista and XP 64. I couldping the server via IP and name but when I try to access the share in Windows Explorer it will give me error 0x80004005. If I choose diagnose it will say the the computer "is not set up to establish a connection on port "File and printer sharing (SMB)" with this computer.

I turned off all Windows firewalls on the server but had the same problem. Looking at ports 139 and 445 using portqry.exe -n server -e 139,445 -p TCP both reports are not listening:
TCP port 139 (netbios-ssn service): NOT LISTENING
TCP port 445 (microsoft-ds service): NOT LISTENING

Looking at port 445 from the server (127.0.0.1) it was listening. Eventually I looked at the properties of my network adapter on the server and release File and Print Sharing, Link Layer Topology, were turned off.

I still don't understand why there wasn't any warning when I turned on file sharing and why joining a domain was affected.

Jeff

.



Relevant Pages

  • VNC connection closed unexpectedly
    ... BlastWave) running on a test server. ... 23/09/05 19:42:22 Listening for VNC connections on TCP port 5901 ... 23/09/05 19:42:22 Listening for HTTP connections on TCP port 5801 ...
    (comp.unix.solaris)
  • VNC connection closed unexpectedly
    ... BlastWave) running on a test server. ... 23/09/05 19:42:22 Listening for VNC connections on TCP port 5901 ... 23/09/05 19:42:22 Listening for HTTP connections on TCP port 5801 ...
    (comp.sys.sun.admin)
  • VNC connection closed unexpectedly
    ... BlastWave) running on a test server. ... 23/09/05 19:42:22 Listening for VNC connections on TCP port 5901 ... 23/09/05 19:42:22 Listening for HTTP connections on TCP port 5801 ...
    (SunManagers)
  • TCP port 135 (epmap service): NOT LISTENING
    ... it was first discovered by failing to log into DHCP mmc on that server ... TCP port 135 (epmap service): NOT LISTENING ...
    (microsoft.public.windows.server.active_directory)
  • Re: Windows Messenger for Exchange 2000 over VPN
    ... If it is TCP port 1503, ... but application sharing does not. ... >> that all communications was between the clients and the server on tcp ...
    (microsoft.public.windowsxp.messenger)