need help: moved Terminal server to new site (new ip) now cant connect

Superficial

Superficial

Superficial

Soldato
Joined
29 Oct 2002
Posts
4,166
Location
London
Hi there,

thanks for reading - no users on the internal LAN can RDP connect after moving to new site with new IP address.

Nothing on the server has been changed at all and it is otherwise as normal and can be pinged and have drives mapped etc.

can anyone help?
 
Was there an access control list limiting connectivity from/to a certain IP?

Check firewall rules accessing RDP for the previous IP.
 
hi thanks for your replies:

the old ip was 192.168.1.13 and the new ip is simply 192.168.2.13

dlockers: would firewall rules effect users on the same internal lan network though?

RE ip ranges - i doubt it.

to elaborate there is a LAN to LAN VPN network between the sites (hence the small change in ip address) therefore all the clients that used to connect are as they were.
 
Last edited:
Superficial said:
Hi there,

thanks for reading - no users on the internal LAN can RDP connect after moving to new site with new IP address.

Nothing on the server has been changed at all and it is otherwise as normal and can be pinged and have drives mapped etc.

can anyone help?
Click to expand...

Without wishing to state the obvious, the ip address has changed. Are the LAN clients now trying to connect to x.x.2.13 or x.x.1.13?
 
tribz said:
And are these LAN connections or VPN ones?
Click to expand...

i actually have now tried both to the same effect. initially it was PC's in the same office and now I have tried it on other VPN's PC's and from another server.

no joy


got a feeling this is something very simple but I'm not pretending to know that much about TS's
 
Superficial said:
i actually have now tried both to the same effect. initially it was PC's in the same office and now I have tried it on other VPN's PC's and from another server.

no joy


got a feeling this is something very simple but I'm not pretending to know that much about TS's
Click to expand...

Are they definitely connecting to an ip and not a host name? If its a host name, I'd check the local computers host file and server DNS.

Very strange if they can ping the ip but not connect to it.
 
tribz said:
Are they definitely connecting to an ip and not a host name? If its a host name, I'd check the local computers host file and server DNS.

Very strange if they can ping the ip but not connect to it.
Click to expand...

yeah - i'm the one doing the connection attemps on their PC's.

I'm literally hoping for a simple facepalm solution. whether it makes me look stupid or not.
 
Superficial said:
yeah - i'm the one doing the connection attemps on their PC's.

I'm literally hoping for a simple facepalm solution. whether it makes me look stupid or not.
Click to expand...

Know the feeling, sometimes you just want it done and dusted.

So if you can map a drive to the server on the new address then the connectivity has to be fine.

The only things left are windows firewall on the TS. Check the rule for anything obvious. Any firewall/av software on the clients that you can disable? Flush the DNS, delete the arp cache?
 
Just off the top of my head and I know you said nothing has changed but.

Is the terminal server service running?
Have you tried restarting the service?
Is port 3389 open?
Have you checked the firewall hasn't somehow been enabled on the network adapter?
Check the registry setting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server fDenyTSConnections is set to 0 ?
Are there any errors in the event viewer pertaining to the RPC server?
I am assuming you have rebooted the server.
 
Zaphrod said:
Just off the top of my head and I know you said nothing has changed but.

Is the terminal server service running?
Have you tried restarting the service?
Is port 3389 open?
Have you checked the firewall hasn't somehow been enabled on the network adapter?
Check the registry setting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server fDenyTSConnections is set to 0 ?
Are there any errors in the event viewer pertaining to the RPC server?
I am assuming you have rebooted the server.
Click to expand...

i missed this:

@ 16:41

One or more Terminal Server Licensing certificates on server xxxxxxx are corrupt. Terminal Server Licensing will only issue temporary licenses until the server is reactivated. See Terminal Server Licensing help topic for more information.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

i had no idea that simply changing the ip address might do this


i could do with some guidance on reinstalling the licesnes - i tried the wizard but it's not working
 
You must log in or register to reply here.
Back
Top Bottom