Posts: 119
Joined: 31.Oct.2001
From: St. Louis MO
Status: offline
Greetings,
Can someone help me out? I'm having a dickens of a time trying to publish a file share on a SharePoint server in a perimeter network. This is necessary to allow our log analyzer to read the IIS logs in-place. Here's a look under the covers:
The first Non-Web Server Publishing Rule is locked down at both ends by custom computer definitions, with a user-defined protocol -- port 445 TCP inbound. The second rule is similar, with a user-defined protocol allowing port 139 TCP inbound. I identified both ports by watching the ISA monitor while running a mount command on the client. I'm sure I'll have to add more definitions later.
But.....I can't even get my foot out the door, so to speak. As the client attempts to connect, the ISA monitor kicks out dozens of messages about "Microsoft CIFS (TCP)" being blocked by the default rule. The source network is "External," but curiously enough, the destination network is "local host."
Other external-to-DMZ web-publishing and non-web publishing server rules, such as HTTP and RDP, are working fine in the face of this misery.
Can anyone help me with this? If you need more information please ask...thank you!
Tim ==
< Message edited by TimTrace -- 25.Feb.2009 6:11:13 PM >
I've never tried to publish SMB, but it does work to a certain extent with Access Rules. However, you have to be careful with NAT, as there are issues with SMB and NAT access. If you can set a route relationship between the source and destination network, you'll have fewer problems (together with using an access rule instead of a publishing rule).