Billion UK Forum

I have replaced my 7800N with 7800DXL and I am very pleased with it.

I have a very unusual problem.

The new router acts as DHCP server and I can connect from main pc to all network devices. But with one exception.

I have two HP microservers. One runs WIndows Server 2012 Essentials and the other runs WIndows 2012 Storage Server. THe WSE2012 is main server for network and the Storage Server is used for backups only.

I can connect to the WSE server using remote desktop connection and by ip address in browser. But I cannot RDC or ip address with the new router to the Storage Server. The strange thing is that I can see it on the network with network apps and I can establish a connection by mapping network drive.

Now I realise this will be due to the settings on the server, but the strange thing is that I can connect with the old router. When I set up a separate wired network with the old router, main pc and server I can easily rdc into the server. I have done this and disabled the firewall but this still doesnt connect when reconnected to the new router.

So in summary the problem is that a network computer only allows network connection with the old router. I realise this may involve complex settings and much more detail than I have provided but does anyone have any experience or suggestions for this type of problem? Googling suggests there may be connection problems as I described but havent found an exact solution.

For what its worth I was also not able to connect to any of the network printers with the new router from pc's until I had removed them all and reinstalled. That was no problem but it seems that installing a new router changes connection ability, even with fixed ip addresses etc.

Have you tried to setup a static IP lease for the storage device, and set the storage device to obtain a IP address automatically?

Yes have tried both. It was always set for static IP but removed it and gave it DHCP obtain IP automatically. Didnt help.

I dont understand that I cannot ping it, yet I can still see the folders through the mapped drive.

I realise this essentially a windows problem, but what I dont understand is why I can access it through the old router but not the new router. I have now done this several times swapping routers and rebooting. What would it be about the old router that it trusted which it does not for the new?

Thanks.

mjbarnard wrote:Yes have tried both. It was always set for static IP but removed it and gave it DHCP obtain IP automatically. Didnt help.

I dont understand that I cannot ping it, yet I can still see the folders through the mapped drive.

I realise this essentially a windows problem, but what I dont understand is why I can access it through the old router but not the new router. I have now done this several times swapping routers and rebooting. What would it be about the old router that it trusted which it does not for the new?

Thanks.

Not sure mate, very strange that you can't ping it, have you tried to restart the device? Does the device show up on the DHCP table once set to obtain a IP address automatically?

I have restarted dozens of times. I have completely disabled the firewall.

It shows up in DHCP both when fixed IP or obtain IP automatically

mjbarnard wrote:I have restarted dozens of times. I have completely disabled the firewall.

It shows up in DHCP both when fixed IP or obtain IP automatically

Well if you can access it, but can't ping it or RDP to it, there must be something blocking you within the settings on your WIndows 2012 Storage Server, ICMP is ping protocol, but the firewall is off, maybe there is a 'Set Network Location' section on WIndows 2012 Storage Server like windows 7, that needs to be adjusted

Yes Im sure you are right. However the problem is that the server is a headless unit so in order to change any settings on it I have to disconnect it from the network, reconnect it to a separate network and pc on the old router so that I can RDP to it. Then I have to power it down and reconnect to the new router and see if it works. These microservers are very slow booters and I am powering up and down the main pc to switch between these networks so this has taken me all day to try multiple times!

I think its time to cut my losses and try either:
1) I have established its easy to attach old router to new router by giving fixed IP, disabling DHCP and using as switch or wireless AP. I could disable wireless on the old router, re-enable DHCP and attach only the problem server to it wired. And use fixed IP (outside of new router DHCP addresses) for server. That way it would get IP from old router which it works but connected to new router network and no IP clashes. That might work and I could then try new settings perhaps more easily if RDP works.

2) More likely cut my losses and either install new OS on server (actually windows 8 would be sufficient and much less costly) or throw the towel in and buy a new HP microserver. They have moved on a couple of generations since I bought mine and I have found them (until changing to this router!) highly reliable and useful.

Thanks anyway.

Just in case anyone else encounters this I have solved it. If you google new router cannot rdp there are a large number of identical situations. As usual most of the solutions are not useful and it takes a fair amount of digging to get it, although the solution is fairly simple.

As billion_fan suggests the key lies in the server2012 network settings. However this is precipitated by the change of router. To the 2012server any DHCP server with a MAC address different to the original router MAC address becomes a Public network. RDC is disabled for public networks, and this would appear to still apply when Firewall disabled! With a headless unit of course it is then impossible to RDC in and adjust the settings.

So the solution was to connect old router and server and single pc together on isolated ethernet network. RDC in and re-enable Firewall via control panel. Then go to advanced settings, adjust rules and enable RDP connections for public networks. Reboot server and connect to new router. Then can RDC in from anywhere on network.

Note that after doing this the network is labelled public on the server2012. It can be changed back to Private (not easily through network and sharing center!) but through clicking the network icon bottom right of desktop, rightclicking network and turning folder sharing to on.

Thanks billion fan for pointing me in the correct direction. From what I can see of other descriptions of the same problem, this is specific to RDC settings on the server.