I have a user that can successfully connect via Pulse, gets a valid IP address and can even ping resources on the network, however when trying to connect to Outlook or RDP to servers it faisl to connect. All other clients are able to connect to so its not a firewall issue within the LAN. Has anyone seen anything like this before?
I also have one other user who can connect but they get no IP address as the Juniper Pulse adapter does not seem to get created??
Is this on Windows XP, with the 7.1 code? If so, I've seen that behavior. Best we could figure, XP and Pulse don't mix on that code base. We couldn't get Outlook to work; it worked fine on Win7 w/ Pulse.
Haven't tested the new 7.2 Pulse (3.0) yet in that kind of environment, for lack of an XP machine I could use. I am curious to know whether Pulse on 7.2 fixes the Outlook issues I saw on XP (in a customer's environment, who still has a lot of XP around).
It is on XP I have tried it on both 7.1 and 7.2 and get the same result. we have 70 other users who are all on XP and have no issues at all.
Interesting. So Pulse on XP is still broken. If you switch to Network Connect, the issue will likely go away.
i'm on xp and use pulse remote without issue for all my accesses (outlook, rdp, vnc, fileshares, etc) and have been usingit since it went internal beta for the same.
if you ping/tracert to the pulse IP, what happens? this same user works on other machines?
It is possible something is being fragmented...
The RDP server(s) that you are trying to connect to can do the ping/tracert to the Pulse device without issue as well as from the Pulse device to the RDP server(s)?
Does the failure follow the user to multiple XP machines OR does it stay on the specific machine(s), regardless of the user who logs in?
Does the same happen on a new profile on the PC?