Posts: 44
Joined: 20.Mar.2002
From: Kirkland, WA
Status: offline
ISA Server setup to allow incoming VPN. External clients can login and connect just fine, but I have never been able to get name resolution to help, even with all the fine help from this message board several months ago. Cliens can connect to anything if they use IP addresses instead of names. And yes, believe me, we have been over all the settings. The client is getting the wins server address.
What I noticed now though, by examining the IP log, is that ISA is blocking attempts of the client to conenct to udp ports 137 and 138, the netbios name service and datagrm protocols. Do I need to configure some kind of incoming rule for these? I did not think these would be needed for a vpn connection to resolve name. . I must be missing something here, but I have never read any kind of instruction about configuring rules for these to get incoming VPN to work. I am sure that I have just displayed brute ignorance here, but I am willing to humuliate myself to solve this problem!
No brute ignorance at all But the ISA Server does not examine the VPN traffic, so ISA Server Protocol Rules do not apply to it. When you do an IPCONFIG on the VPN client, it does't show the IP address of the WINS server?
Posts: 44
Joined: 20.Mar.2002
From: Kirkland, WA
Status: offline
Hi Tom.
That is what I thought. And IPCONFIG does show the WINS server which is assigned from the ISA internal NIC. Everything looks good, but name resolution just does not work, so no browsing. It is a pain to show our users how to do a "net use" with IP addresses!
Posts: 44
Joined: 20.Mar.2002
From: Kirkland, WA
Status: offline
Tom,
These are Win2000 and XP clients. I have a further clue: After the client connects, The network can be browsed and the servers and PC's show up. But when you try to access a server to see the shares, by double clicking the server icon or mapping a drive, then you get the dreaded "Network path cannot be found" error.
But if you map a drive using the IP address of the server as in \\192.168.10.30\share, then you are prompted for credentials and the drive is mapped, and it works.
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [ISA Server 2000 Firewall] >> VPN >> udp 137, 138 
udp 137, 138 - 
![[Big Grin]](/image/smiles/biggrin.gif)
But the ISA Server does not examine the VPN traffic, so ISA Server Protocol Rules do not apply to it. When you do an IPCONFIG on the VPN client, it does't show the IP address of the WINS server?![[Roll Eyes]](/image/smiles/rolleyes.gif)
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread