Greetings,
I am setting up a few remote workstations over an ipsec vpn tunnel. I ran into a problem where I am not able to logon and browse the domain effectively. Doing some research, I found that my win2k sbs server is not listening on port 445 (as reported by netstat and tcpmon, smb port microsoft-ds)
My step is to remove file and print sharing but have not done so yet. I have run the iis lockdown tool, I have never heard of this port being disabled or secured by a ms tool. There is a way to edit the registry to disable 445 service but the keys are all intact.
On the remote machines, I have enabled netbios over tcpip, thinking they should try to connect on 137/139, but they do not seem to be doing so and logon is taking 15 minutes and the machines are still unable to browse the network. I have pointed both wins and dns soley to the ntserver with no results.
The weird part is, the local machines are working ok, I am assuming they are rolling over to 139. Is there a way to force the remote workstations to use 139 and not 445 temporaily while I resolve the 445 issue?
Thanks
Jason
I am setting up a few remote workstations over an ipsec vpn tunnel. I ran into a problem where I am not able to logon and browse the domain effectively. Doing some research, I found that my win2k sbs server is not listening on port 445 (as reported by netstat and tcpmon, smb port microsoft-ds)
My step is to remove file and print sharing but have not done so yet. I have run the iis lockdown tool, I have never heard of this port being disabled or secured by a ms tool. There is a way to edit the registry to disable 445 service but the keys are all intact.
On the remote machines, I have enabled netbios over tcpip, thinking they should try to connect on 137/139, but they do not seem to be doing so and logon is taking 15 minutes and the machines are still unable to browse the network. I have pointed both wins and dns soley to the ntserver with no results.
The weird part is, the local machines are working ok, I am assuming they are rolling over to 139. Is there a way to force the remote workstations to use 139 and not 445 temporaily while I resolve the 445 issue?
Thanks
Jason