Unable to connect to port 445

Hello,

I am unable to connect to port 445 on a WIndows 2003 SP2 DC. We do not have
the firewall enabled. Nestat shows the system listening on TCP port 445 but I
do not see any service listening on UDP 445. I see both TCP and UDP on our
other DCs just not this one.

I checked the NetBT parameters in the registry and do not see anything amiss.

Any ideas on how to resolve this?

Thanks

"PFCU" <> wrote in message
news:691E5678-B090-4851-86E2-...
> Hello,
>
> I am unable to connect to port 445 on a WIndows 2003 SP2 DC. We do not
> have
> the firewall enabled. Nestat shows the system listening on TCP port 445
> but I
> do not see any service listening on UDP 445. I see both TCP and UDP on our
> other DCs just not this one.
>
> I checked the NetBT parameters in the registry and do not see anything
> amiss.
>
> Any ideas on how to resolve this?
>
> Thanks


How exactly are you trying to connect and for what purpose?

FYI, TCP 445, also called DirectSMB, is tried first (default) prior to
NetBIOSvTCP 139 for UNC, mapped drives, and other communications. So I am
not exactly sure what you mean you are unable to connect. Can you map a
drive? If both systems are Windows 2000 and newer and not using WINS, and a
mapped drive or UNC connection is successful, then you've connected using
TCP 445. Use a network capture tool to verify.


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

"PFCU" <> wrote in message
news:691E5678-B090-4851-86E2-...
> I am unable to connect to port 445 on a WIndows 2003 SP2 DC. We do not
> have
> the firewall enabled. Nestat shows the system listening on TCP port 445
> but I
> do not see any service listening on UDP 445. I see both TCP and UDP on our
> other DCs just not this one.

You don't connect to ports,..you connect to Applications. A port is nothing
but a Layer4 Address that identifies a "listening" Application. You have to
connect to the Application in a proper way with the proper "client" that
means something to the Application you are interacting with. Telnet does
not universally serve that purpose, it does not automatically do the correct
handshaking proceedures at the Application level.

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------