Terminal Server agent internet not working

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Terminal Server agent internet not working

L3 Networker
Hi Team,
 
We have configured the terminal server agent and tested it out for few agents and it was successful. But, for the same user's internet was not working some times. Agents version is the latest version.
 
Have checked the source port allocation and their count is not exceeded. But still, somewhere it's misbehaving in mapping the IP-user-port.
 
 
 
Regards,
Vishnu PS.
1 accepted solution

Accepted Solutions

post checking the captures from Wireshark we noticed that no traffic was even being initiated from the machine. We checked the proxy settings and noticed that the browser was set to use a local proxy which was not available. I suspected this to be the cause of the problem as the proxy settings were disabled for the working set of users. When we tried to check the internet access from Internet explorer the error was visible and the traffic was indeed being sent to proxy and that looked to be the reason why the internet access did not work.

 

user the proxy was disabled and we were seeing some transactions being triggered on wireshark for the page access however the page was not loading. When we checked the captures we noticed that only a ssl handshake had completed but no other requests were seen. We proceeded to decrypt the traffic and there we noticed that for the failed transactions no HTTP GET request was seen and for the working ones the “HTTP GET: request was seen. The problem was more specifically seen with Chrome. We proceeded to check with “IE” and with IE the page loaded every time we tried to access it. This indicated that this was again a client end issue possibly with the GPO settings causing chrome to not even trigger the HTTP GET requests when the traffic did not work.

 

Regards,

Vishnu

View solution in original post

8 REPLIES 8

Cyber Elite
Cyber Elite

@VishnuPS,

What exactly is the issue? If you look in the logs, is the user-id dropping for users after a set time period, is the agent failing to register the user with the firewall when they login, or something else? 

Users are able to connect, but the internet not working for some users.

We have configured the user-based policy. 

 

Regards,

Vishnu PS.

Is there a source port allocation on the terminal server agent for these users? Are the terminal server agents connected successfully on the firewall? Do you see the internetconnections in the firewall log? Are there source users in these logs?

Terminal agents connected with firewall successfully. Users are able o connect.

 

Some user's internet not working also no getting logs in the firewall but I can see in the CLI that users are connected in the Terminal agent.

But it works for other users on the same terminal servers? For the users who are not able to connect to the internet, are they able to ping an IP in the internet or is the problem mainly with accessing websites in a browser?

Hi , I have raised the TAC case regarding this case. I will update you once its resolved.

L0 Member

Any update from TAC?

We have similar issue.

post checking the captures from Wireshark we noticed that no traffic was even being initiated from the machine. We checked the proxy settings and noticed that the browser was set to use a local proxy which was not available. I suspected this to be the cause of the problem as the proxy settings were disabled for the working set of users. When we tried to check the internet access from Internet explorer the error was visible and the traffic was indeed being sent to proxy and that looked to be the reason why the internet access did not work.

 

user the proxy was disabled and we were seeing some transactions being triggered on wireshark for the page access however the page was not loading. When we checked the captures we noticed that only a ssl handshake had completed but no other requests were seen. We proceeded to decrypt the traffic and there we noticed that for the failed transactions no HTTP GET request was seen and for the working ones the “HTTP GET: request was seen. The problem was more specifically seen with Chrome. We proceeded to check with “IE” and with IE the page loaded every time we tried to access it. This indicated that this was again a client end issue possibly with the GPO settings causing chrome to not even trigger the HTTP GET requests when the traffic did not work.

 

Regards,

Vishnu

  • 1 accepted solution
  • 4679 Views
  • 8 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!