Avatar of Benview
Benview
Flag for Australia asked on

SBS-E 2011 - Can't Remote Access just one Computer Name

I have a just implemented an SBS Essentials 2011 network with 12 PCs (mix of XP and W7). Remote access is working OK except for just one PC.

Computer "XXXXWS001" won't proceed past the "Initiating remote connection..."
and eventually gives the error message
    "Remote desktop can't find the computer "XXXXWS001" This might mean
     that "XXXXWS001" does not belong to the specified network..........
The SBS-E Dashboard sees the computer OK and I have added the computer access to the appropriate users.

In desperation I removed the computer from the network, changed its ID to "XXXXWS013" and re-connected it to the network using the connect wizard.
This time remote access worked fine!

Unfortunately I need to get "XXXXWS001" working as a software app is using preset PC IDs as a licence check.

I thought, just a hipcup with the first experience so I disconnected "XXXXWS013" and renamed the computer back to "XXXXWS001" and connected it again using the wizard.
Remote access did not work!!!!

So, "XXXXWS013" does work but  "XXXXWS001" refuses to work.
(I have 11 other PCs working fine)

I have looked for a loose end both local and at the server but I'm lost ... any thoughts where to look and what to look for?

Thanks
Microsoft Legacy OSSBSWindows 7

Avatar of undefined
Last Comment
Olaf De Ceuster

8/22/2022 - Mon
SOLUTION
epohl

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
SOLUTION
Olaf De Ceuster

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
Benview

ASKER
Thanks epohlolafdc for the quick response:

I found that I can connect to XXXXWS001 using RDP but, only using its local IP  not using its computer name.

I checked the router, the IP is within scope.
I have run the commands suggested by olafdc.... they all seemed to process OK but the result is still the same .... cannot remote access XXXXWS001 using the computer name.

My router and SBS-E do not see eye-to-eye on UPnP but as 11 other PCs do remote access OK I did not see this as an issue. When I Disabled the network card it tried to tell me it couldn't because of UPnP but it did disconnect and re-enabled OK. (Broadcom NetExtreme 57xx)

Any other ideas?
Olaf De Ceuster

Issue is defenitely DNS.
Can you make a manual A record?
Olaf
ASKER CERTIFIED SOLUTION
thomasclm

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
Benview

ASKER
OK thomasclm we're getting warmer.......

C:\>nslookup XXXXWS001
Server:   UnKnown
Address:  192.168.1.200                    (This is the server)
Name:    XXXXWS001.DOMAIN.Local
Address:  192.168.0.24                      (This is incorrect it should be 192.168.1.150)

I tried the other computer names and the correct IPs were returned.

I recognise the incorrect address... it comes from the router environment where the SBS Essentials server was set up with a test PC before moving to live. I thought I removed all traces of that DHCP.

As olafdc suggested above I have done a ipconfig /flushdns at the server but without success.... I have looked everywhere but just cannot find 192.168.0.24 within the server.... there must be somewhere yet to look.....or other commands to run at the server!

Suggestions
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
thomasclm

Login to  XXXXWS001 and make sure its pointing to your correct DNS server as preferred DNS Server and go to command prompt and execute  "ipconfig /registerdns".
Try "nslookup XXXXWS001" to ensure its resolving to correct IP.

Else you can manually edit the HOST (A) record in dns server with the correct IP.
Benview

ASKER
SUCCESS

I found an old reference to XXXXWS001 - 192.168.0.24 in the server ForestDnsZone....once I cleaned this out and made sure nslookup XXXXWS001 at the computer was returning the correct IP - 192.168.1.150 then Remote Access using the computer name was successful.

I've learnt some!!!!

Thanks to all for your help today .. everyone was pointing me toward a DNS solution
Olaf De Ceuster

If you can't make a maunual A record you  can uninstall the nic or nics (if you have wireless too) and restart the computer.
The N
Nic will automatically reinstall but all cache will be deleted.
This will tell you if issue is with workstation or server.
Olaf
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.