Can't map a drive to a DC

I've seen this several times now; I can't map a drive to a remote win2003
SP1 DC from an XP pro SP2 client. By "remote" I mean they're on different
domains & LANs that are connected by a HW firewall.

However, I can log on via Remote Desktop to the remote DC and map a drive
back to my local DC on my LAN. So I assume it's not a matter of some
necessary port being blocked, e.g.; 137-139 for netlogon.

Anyone have a suggestion?

thanks!

When you share your drive via Remote Desktop it does not use the regular
ports, but all SMB traffic is tunneled thru port 3389 (Remote Desktop). So I
assume it could still be that the FW is blocking necessary ports, such as
UDP/137, UDP/138, TCP/139 or TCP/445. And remember that RPC will still not
work over such a firewall due to its nature. (A client initiating the RPC
connects to the RPC portmapper service on the server which will return a
"seemingly random" port number over 1024 through which the communication will
take place.)

Martin Szalay

"BLMuzzy" wrote:

> I've seen this several times now; I can't map a drive to a remote win2003
> SP1 DC from an XP pro SP2 client. By "remote" I mean they're on different
> domains & LANs that are connected by a HW firewall.
>
> However, I can log on via Remote Desktop to the remote DC and map a drive
> back to my local DC on my LAN. So I assume it's not a matter of some
> necessary port being blocked, e.g.; 137-139 for netlogon.
>
> Anyone have a suggestion?
>
> thanks!
>
>
>

Thanks for the comment. I *thought* the VPN was set to block no ports.
That's what the configuration tells it to do "enable windows networking
(NetBIOS) broadcasts". I checked with Sonicwall, the FW mfr. and followed
the instructions in their doc on the matter. I opened a case with them and
they didn't have an immediate answer. I'll report back for the sake of
completeness.

thanks!


"MartonSz" <(E-Mail Removed)> wrote in message
news:5E95925B-4087-4A74-BD6E-(E-Mail Removed)...
> When you share your drive via Remote Desktop it does not use the regular
> ports, but all SMB traffic is tunneled thru port 3389 (Remote Desktop). So
> I
> assume it could still be that the FW is blocking necessary ports, such as
> UDP/137, UDP/138, TCP/139 or TCP/445. And remember that RPC will still not
> work over such a firewall due to its nature. (A client initiating the RPC
> connects to the RPC portmapper service on the server which will return a
> "seemingly random" port number over 1024 through which the communication
> will
> take place.)
>
> Martin Szalay
>
> "BLMuzzy" wrote:
>
>> I've seen this several times now; I can't map a drive to a remote win2003
>> SP1 DC from an XP pro SP2 client. By "remote" I mean they're on
>> different
>> domains & LANs that are connected by a HW firewall.
>>
>> However, I can log on via Remote Desktop to the remote DC and map a drive
>> back to my local DC on my LAN. So I assume it's not a matter of some
>> necessary port being blocked, e.g.; 137-139 for netlogon.
>>
>> Anyone have a suggestion?
>>
>> thanks!
>>
>>
>>

the firewall appears to be configured correctly. I can map a drive to a
w2003 server in a workgroup but not to one that's a DC in a different
domain.

still perplexed,

blm


"BLMuzzy" <(E-Mail Removed)> wrote in message
news:eGQ$(E-Mail Removed)...
> Thanks for the comment. I *thought* the VPN was set to block no ports.
> That's what the configuration tells it to do "enable windows networking
> (NetBIOS) broadcasts". I checked with Sonicwall, the FW mfr. and followed
> the instructions in their doc on the matter. I opened a case with them
> and they didn't have an immediate answer. I'll report back for the sake
> of completeness.
>
> thanks!
>
>
> "MartonSz" <(E-Mail Removed)> wrote in message
> news:5E95925B-4087-4A74-BD6E-(E-Mail Removed)...
>> When you share your drive via Remote Desktop it does not use the regular
>> ports, but all SMB traffic is tunneled thru port 3389 (Remote Desktop).
>> So I
>> assume it could still be that the FW is blocking necessary ports, such as
>> UDP/137, UDP/138, TCP/139 or TCP/445. And remember that RPC will still
>> not
>> work over such a firewall due to its nature. (A client initiating the RPC
>> connects to the RPC portmapper service on the server which will return a
>> "seemingly random" port number over 1024 through which the communication
>> will
>> take place.)
>>
>> Martin Szalay
>>
>> "BLMuzzy" wrote:
>>
>>> I've seen this several times now; I can't map a drive to a remote
>>> win2003
>>> SP1 DC from an XP pro SP2 client. By "remote" I mean they're on
>>> different
>>> domains & LANs that are connected by a HW firewall.
>>>
>>> However, I can log on via Remote Desktop to the remote DC and map a
>>> drive
>>> back to my local DC on my LAN. So I assume it's not a matter of some
>>> necessary port being blocked, e.g.; 137-139 for netlogon.
>>>
>>> Anyone have a suggestion?
>>>
>>> thanks!
>>>
>>>
>>>
>
>