Search results for query: *

@PaulRoM - I think I might be missing what would make it easier if the two IP 500's are next to each other. How does it make calling each other easier? As for Option 2, so I need another IP 500, a PRI into it, a networking license in the main IP 500.. probably a couple others (?) ... any other...

Ok, thanks. Another point came up... Would the two units then connect via the LAN ports and send calls over the fiber? Actually I think I might have figured it out: use SCN for the ext and to send those calls over the LAN, but for outbound calls, send them out of the PRI that is attached on...

I have a client with IP Office, an IP 500 (just one) in a single building right now. They are rapidly approaching 384 users and have a second building next door they are expanding into. The two buildings are connected by a fiber link (point to point) between the buildings. My questions...

I feel like I should apologize for wasting everyone's time, I track it down. It was Remote Access Policies. A previous IT guy had set it up to restrict packets and RDP to ONE computer if the person was part of a particular group. Thanks for all of your pointers. -Ed

When the Domain User VPNs in, you CANNOT telnet to port 3389 or even ping the machine. A Domain Admin CAN ping and telnet port 3389. The Domain User in question is also part of the Remote Desktop Full group as well. The Domain User can VPN to the server though, and VPN into the machine in...

But which group simply stops a person from even telnetting to port 3389 on a computer when they VPN in? The Domain User is not even getting to the login prompt when VPN'ed in and trying to RDP directly to it. -Ed

Odd problem here on a network that I inherited: a Domain Admin can VPN into this network, and then RDP to this Windows XP Pro machine and login with this account that is already logged in on the machine, running apps, etc. But a Domain User VPNs in, and cannot RDP to the XP Pro machine...