slow access using port 445

server A runs an application to process a file on server B. It generates
lots of traffic back and forth between both servers. Server A and Server B
are on LAN. Server C is across WAN. When server A ran the process it
connected to server B using netbios-ssn on port 139. It took about 1 minute.
When server C ran the process (across WAN) it connected to server B using
microsoft-ds (SMB on TCP) on port 445. It was very slow, took almost 20
minutes.

Have no idea what cause the slowness. Is that expected using port 445? Or
does the port make any difference?

Using MS network monitor I also saw that when using port 139 the process
went through 90-100 items each time instead 8 when using port 445.

Thanks in advance.

P.S. I also realized that when mapping a drive across WAN it uses port 445
for connection. Is that correct? Or port 139 is blocked. My network admin
told me that we don't block any port for LAN and WAN.

"Chris" wrote:

> server A runs an application to process a file on server B. It generates
> lots of traffic back and forth between both servers. Server A and Server B
> are on LAN. Server C is across WAN. When server A ran the process it
> connected to server B using netbios-ssn on port 139. It took about 1 minute.
> When server C ran the process (across WAN) it connected to server B using
> microsoft-ds (SMB on TCP) on port 445. It was very slow, took almost 20
> minutes.
>
> Have no idea what cause the slowness. Is that expected using port 445? Or
> does the port make any difference?
>
> Using MS network monitor I also saw that when using port 139 the process
> went through 90-100 items each time instead 8 when using port 445.
>
> Thanks in advance.

"Chris" <(E-Mail Removed)> wrote in message news:7B70F065-4921-426F-867F-(E-Mail Removed)...
> P.S. I also realized that when mapping a drive across WAN it uses port 445
> for connection. Is that correct? Or port 139 is blocked. My network admin
> told me that we don't block any port for LAN and WAN.
>
> "Chris" wrote:

DirectSMB (port 445) is what provides support in an environments without NetBIOS. It shouldn't take that long to connect.

Is your environment using WINS? Run an ipconfig /all and see if there's a WINS address.

When you open Network Neighborhood, can you see ServerC across the WAN?

--
Ace

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

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
(E-Mail Removed)

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

"Efficiency is doing things right; effectiveness is doing the right things." - Peter F. Drucker
http://twitter.com/acefekay

Ace,
We don't use WINS. I have no problem to map a drive to ServerC across
WAN. But I can't see ServerC in Network Neighborhood across WAN. I guess
it's because we don't use WINS and routers blocked broadcasting.

I have tried to disable port 445 on ServerB that made RPC shut down so can't
connect to it using UNC anymore. So, that's didn't work.

Then I tried to disable Netbios Over IP. It disabled port 139. All
connections to ServerB were using Microsoft-DS, which is on port 445. That
made no difference for the process, either on LAN or WAN.

I'll try to set up lmhost on each server see if it makes any difference. I
also think my problem is due to the network latency on WAN. How can I check
what is my latency and if it's normal or not?

Thanks.

"Chris" wrote:

> P.S. I also realized that when mapping a drive across WAN it uses port 445
> for connection. Is that correct? Or port 139 is blocked. My network admin
> told me that we don't block any port for LAN and WAN.
>
> "Chris" wrote:
>
> > server A runs an application to process a file on server B. It generates
> > lots of traffic back and forth between both servers. Server A and Server B
> > are on LAN. Server C is across WAN. When server A ran the process it
> > connected to server B using netbios-ssn on port 139. It took about 1 minute.
> > When server C ran the process (across WAN) it connected to server B using
> > microsoft-ds (SMB on TCP) on port 445. It was very slow, took almost 20
> > minutes.
> >
> > Have no idea what cause the slowness. Is that expected using port 445? Or
> > does the port make any difference?
> >
> > Using MS network monitor I also saw that when using port 139 the process
> > went through 90-100 items each time instead 8 when using port 445.
> >
> > Thanks in advance.

"Chris" <(E-Mail Removed)> wrote in message news:F4C76E34-5791-4D86-8C84-(E-Mail Removed)...
> Ace,
> We don't use WINS. I have no problem to map a drive to ServerC across
> WAN. But I can't see ServerC in Network Neighborhood across WAN. I guess
> it's because we don't use WINS and routers blocked broadcasting.
>
> I have tried to disable port 445 on ServerB that made RPC shut down so can't
> connect to it using UNC anymore. So, that's didn't work.
>
> Then I tried to disable Netbios Over IP. It disabled port 139. All
> connections to ServerB were using Microsoft-DS, which is on port 445. That
> made no difference for the process, either on LAN or WAN.
>
> I'll try to set up lmhost on each server see if it makes any difference. I
> also think my problem is due to the network latency on WAN. How can I check
> what is my latency and if it's normal or not?

I'm suprised you are not using WINS in a multi-subnetted environment. It is rather simple to setup, much easier than dealing with lmhosts files. THis is why you can't see the other subnet(s) in the neighborhood. And you don't want to disable 445. It is a necessary port.

As for latency, you will need to setup an app that will pull data from your routers, such as PRTG and analyze it based on what the connectionj speed is and what you are actually seeing.
http://www.paessler.com/prtg/?utm_ca...FRSfnAodaj-QzQ

Ace

Thanks. I'll play with prtg.

"Ace Fekay [Microsoft Certified Trainer]" wrote:

> "Chris" <(E-Mail Removed)> wrote in message news:F4C76E34-5791-4D86-8C84-(E-Mail Removed)...
> > Ace,
> > We don't use WINS. I have no problem to map a drive to ServerC across
> > WAN. But I can't see ServerC in Network Neighborhood across WAN. I guess
> > it's because we don't use WINS and routers blocked broadcasting.
> >
> > I have tried to disable port 445 on ServerB that made RPC shut down so can't
> > connect to it using UNC anymore. So, that's didn't work.
> >
> > Then I tried to disable Netbios Over IP. It disabled port 139. All
> > connections to ServerB were using Microsoft-DS, which is on port 445. That
> > made no difference for the process, either on LAN or WAN.
> >
> > I'll try to set up lmhost on each server see if it makes any difference. I
> > also think my problem is due to the network latency on WAN. How can I check
> > what is my latency and if it's normal or not?
>
> I'm suprised you are not using WINS in a multi-subnetted environment. It is rather simple to setup, much easier than dealing with lmhosts files. THis is why you can't see the other subnet(s) in the neighborhood. And you don't want to disable 445. It is a necessary port.
>
> As for latency, you will need to setup an app that will pull data from your routers, such as PRTG and analyze it based on what the connectionj speed is and what you are actually seeing.
> http://www.paessler.com/prtg/?utm_ca...FRSfnAodaj-QzQ
>
> Ace
>

"Chris" <(E-Mail Removed)> wrote in message news8B555FC-8C1E-45F2-83CB-(E-Mail Removed)...
> Thanks. I'll play with prtg.

You are welcome!

Ace