PortN0X
asked on
Terminal Server Remote App, Wireless Access point issue
Hello,
We are having an issue with our Terminal Server Remote Application that is used on Mobile Med Carts. These med carts have wireless that connect to WAP's throughout the building. We are noticing an issue with the med carts and the remote app, when the med cart switches between WAP's the remote app will freeze and sometimes close down completely. not all waps are separate(not managed by a central device), so the med carts don't switch between waps like a managed wifi would provide.
Is there anything that we could do to help the freezing issue we are experiencing. Note 3/4 of the wap's are not N capable, two of them were replaced with N capable waps.
Would getting a managed wireless setup fix our issue? Is there anything on the med cart thin client that could be changed to make the switching between wap's faster? To note we have the med carts all set with Static IP's to try and help speed up the wap to wap connection so it isn't having to try and check for dhcp and pull a new ip each time.
Also to help with the Terminal Server App from ending the session we have changed the end session from one minute to five minutes.
Any ideas or suggestions would be greatly appreciated.
We are having an issue with our Terminal Server Remote Application that is used on Mobile Med Carts. These med carts have wireless that connect to WAP's throughout the building. We are noticing an issue with the med carts and the remote app, when the med cart switches between WAP's the remote app will freeze and sometimes close down completely. not all waps are separate(not managed by a central device), so the med carts don't switch between waps like a managed wifi would provide.
Is there anything that we could do to help the freezing issue we are experiencing. Note 3/4 of the wap's are not N capable, two of them were replaced with N capable waps.
Would getting a managed wireless setup fix our issue? Is there anything on the med cart thin client that could be changed to make the switching between wap's faster? To note we have the med carts all set with Static IP's to try and help speed up the wap to wap connection so it isn't having to try and check for dhcp and pull a new ip each time.
Also to help with the Terminal Server App from ending the session we have changed the end session from one minute to five minutes.
Any ideas or suggestions would be greatly appreciated.
To follow up with what @hecgomrec said...are all your SSID's the same? They should be to allow the client devices to roam correctly between each access point...if they are DIFFERENT SSID's then this takes longer to connect/disconnect...which
ASKER
Thanks for the responses...
Notes...
Yes all SSID are named the same, with the same password.
hecgomerc.... In my mind if I bypassed the lan/ip issue by creating a exclusion list in dhcp, and by setting each cart up with a Static IP, that way they don't have to go looking for an IP each time they move between WAP's. Am I correct in this thinking, sound like the same as what you said.
Also we currently are not letting any other devices on the wireless right now because of the issues. Only ones that did were employee's person devices but they access the guest wifi and the ips of course are on different lan's, separated via vlan.
Notes...
Yes all SSID are named the same, with the same password.
hecgomerc.... In my mind if I bypassed the lan/ip issue by creating a exclusion list in dhcp, and by setting each cart up with a Static IP, that way they don't have to go looking for an IP each time they move between WAP's. Am I correct in this thinking, sound like the same as what you said.
Also we currently are not letting any other devices on the wireless right now because of the issues. Only ones that did were employee's person devices but they access the guest wifi and the ips of course are on different lan's, separated via vlan.
Sounds correct...yes setting the devices with static ip's should get around the request for new ip's when it switches from AP to AP...but then maybe the issue isn't the hand off - does your application need 100% connectivity? I know database apps are like this, meaning this is an application issue and not a network issue...
That is correct, the issue is because every time they swap WAPs their IP might be changed. This in the case your access points are just pass through.
My recommendation is to create a separate LAN for those devices, something similar to the "guest" access you mentioned but this one you can add it to your LAN routing table and the router will handle both LANs on the same cable (not vlan) allowing you to have some kind of "privacy" on your LAN while the remote devices still have access to shares on it only if they now their name and address as they won't find them as a regular share unless you have a special software to detect LANs on the cable... :-)
Anyways, if you don't have that many devices and you can spare some IPs, give those devices a fixed IP from a range that is excluded from your DHCP server scope and try them.
My recommendation is to create a separate LAN for those devices, something similar to the "guest" access you mentioned but this one you can add it to your LAN routing table and the router will handle both LANs on the same cable (not vlan) allowing you to have some kind of "privacy" on your LAN while the remote devices still have access to shares on it only if they now their name and address as they won't find them as a regular share unless you have a special software to detect LANs on the cable... :-)
Anyways, if you don't have that many devices and you can spare some IPs, give those devices a fixed IP from a range that is excluded from your DHCP server scope and try them.
ASKER
Few more notes...
The application is run via Terminal Server Remote app's, so connection to the app is needed to run the session. So yes 100% connection is needed.
hecgomrec... I might not have been very clear in my last post, but the LAN's Office/Guest are separate via different vlan's so the guest network is completely separate and the office lan is private meaning Guess users can't access the Office network. And as stated above I already have static ip's setup on those devices and those ip's are excluded.
The application is run via Terminal Server Remote app's, so connection to the app is needed to run the session. So yes 100% connection is needed.
hecgomrec... I might not have been very clear in my last post, but the LAN's Office/Guest are separate via different vlan's so the guest network is completely separate and the office lan is private meaning Guess users can't access the Office network. And as stated above I already have static ip's setup on those devices and those ip's are excluded.
ASKER
Sorry for my ignorance, but could the software on the med carts be a issue where they don't switch fast enough, could a upgrade in software help? Meaning if the software controlling the wifi connection on the med cart, could be
Sorry for my ignorance but could the wifi software on the med carts be an issue. Could we change the software or upgrade it to make the switching between waps faster from the cart stand point. Also could the wap's whether be hardware or software cause the the carts connection to the wap to be slower?
Sorry for my ignorance but could the wifi software on the med carts be an issue. Could we change the software or upgrade it to make the switching between waps faster from the cart stand point. Also could the wap's whether be hardware or software cause the the carts connection to the wap to be slower?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok all.. Thanks for the input everyone.
Ok on to figuring out what managed wifi/a Zero-Handoff Wifi Solution to purchase.
Thanks a bunch for everyone's input.
Ok on to figuring out what managed wifi/a Zero-Handoff Wifi Solution to purchase.
Thanks a bunch for everyone's input.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
The machine was connecting fine to the WAPs but it was changing IP from one to another.
So I end up putting a fix IP on the machine and problem solved.
Now, this did not fix the problem for other mobiles devices, so I had to create another LAN to give those mobile devices full movement too; In my case I configured the access points to give a certain scope of IPs preventing them to overlap and kept the laptop outside of any of the scopes but inside the LAN.
LAN : 192.168.10.0 ~ 192.168.10.254
Laptops: 192.168.10.1 ~ 192.168.10.20
Scopes started at 192.168.10.21 -
So any phone or tablet will get an IP where they are regardless where they first got their IP they will still connected with that IP until they have to renew.
Ooops!... I forgot... the name and password of each access point have to be the same.