No announcement yet.

Using Dynamic TCP ports rather than port 445

  • Filter
  • Time
  • Show
Clear All
new posts

  • Using Dynamic TCP ports rather than port 445

    Say I'm using the Windows AT command service to a remote Windows machine. Is it possible to somehow convince the Scheduler Service to use dynamic ports over TCP rather than well known port 445 over SMB?

    I've tried changing HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\NetBT\Parameters from \Device\ to empty and/or Disabling NetBIOS over TCP/IP in the Advanced TCP/IP Settings Dialog box under the WINS tab without success.

    Please note that Jean-Baptiste Marchand has the following page that indicates that the AT service supports both named pipes (RPC over SMB) and (RPC over) TCP 02.html

    I'm trying to use regmon to see what reg entries at.exe (on the client) reads that may control the transport but haven't found anything yet.

    Any ideas, suggestions or relevant web links are GREATLY appreciated.