01-30-2012 01:45 AM
Secure access 4500 - v7.1
I'm trying to use wsam and Nas ( NT4 compatible). The NAS server is Netapp appliance which is configured with NT4 compatibility: the appliance only listen on TCP port 139 (Not 445).
When I browse the file shares from the lan, the communication uses TCP port 139.
I have configured SA wsam with "wsam Destination" and "Netbios Application". It seems wsam try only to connect on port 445. And so I have an error message on Windows : "The specified network name is no longer available".
Does it mean WSam only want to use TCP port 445 for file sharing and don't use port 139 if 445 is not available?
01-30-2012 06:38 PM
With WSAM in destination mode you should be able to specify the server and the required ports. Try adding port 139 and 445, ensure that you have appropriate ACLs on the SA to allow these ports.
01-31-2012 01:24 AM
WSAM destinations and ACL are set with servers and TCP ports 139,445.
Laptop OS is windows XP, NT integrated, If I open a windows session with NT credential, I can't connect on file sharing
On an other AD integated Laptop If I open a windows session with AD credential, I can connect on file sharing.
In both cases I use the same Secure Access user with same roles (WSAM destinations etc.).
02-06-2012 12:24 AM
On the same laptop, with the same secure access account and the same roles:
If I open a windows session with a NT4 member login , and then launch secure access and WSAM, I can't access to the NAS server.
If I open a windows session with an Acitve Directory account, I can access to the NAS server.
(I set the netbios name in the wsam destinations).
02-09-2012 06:39 AM
I would recommend opening a case with JTAC. I think WSAM should be able to fallback to 139 if 445 is not reachable; do you see any response from the server on 445 when you check the IVE TCP dump?
What do "NT4 member login" and "Active Directory account" refer to: the credentials you use to map the drive OR the credentials used to login to the PC?
02-09-2012 06:56 AM
I've opened a case.
When I use a Windows XP which is integrated in a NT4 domain, I can't reach the shares.
If I use a Windows XP which is integrated in a AD domain, I can reach the shares.
In the both cases, I use the same account (this account is part of an other directory, not a NT4 login or AD login) to log in the secure access, with the same roles and the same wsam profiles.
It seems the Windows XP which is integrated in a NT4 domain acts differently with netbios session serivce and in this case the WSAM proxy don't intercept the traffic.
02-09-2012 09:34 AM
Ok, thank you.
The credentials used to login to secure access will not impact this in any way as that does not touch the credentials used for WSAM-based access; it does look like there is something different on the OS.