RE: Remote Access Issue
- From: Gramps98 <Gramps98@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 23 Jul 2007 10:14:03 -0700
Robert,
You have completely resolved my issue! I also learned a whole lot in the
process, so double thanks!
After making the necessary changes in the DHCP console and re-joining
several PC's to the domain, all of my workstations now respond to the name/IP
address that they're supposed to. It's a beautiful thing!
I'm off to the next issue now...Many thanks for your time and assistance.
-
Gramps98
"Robert Li [MSFT]" wrote:
Hi,.
I am sorry for the delay due to the weekend.
From your description, I noticed the records are not updated automatically
in DNS.
In the default setting, the DHCP server do not update the A record for the
client. The client will update the A record itself and the DHCP server will
help the client to update the PTR record. Please check the following:
1. Open DHCP console.
2. Right click your scope and select Properties.
3. Click DNS
4. Click "Always Dynamically Update DNS A and PTR recorders"
5. Click "Discard A and PTR records when lease is expired"
Hope the information helps.
If you need further assistance, please don't hesitate to let me know.
Best regards,
Robert Li(MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
<Thread-Topic: Remote Access Issue
<thread-index: AcfK/xHbIwwvGy/jTYyFvQ9vIE3zxA==
<X-WBNR-Posting-Host: 207.46.193.207
<From: =?Utf-8?B?R3JhbXBzOTg=?= <Gramps98@xxxxxxxxxxxxxxxxxxxxxxxxx>
<References: <31C459AF-EBC5-4C42-93A3-F3B920FAC585@xxxxxxxxxxxxx>
<ORH4#4eyHHA.6140@xxxxxxxxxxxxxxxxxxxxxx>
<97D9D9FC-70B2-472A-A17A-1EC78DDFE151@xxxxxxxxxxxxx>
<Q3r#yXsyHHA.4200@xxxxxxxxxxxxxxxxxxxxxx>
<Subject: RE: Remote Access Issue
<Date: Fri, 20 Jul 2007 11:52:06 -0700
<Lines: 320
<Message-ID: <260BA699-5EF1-43E6-BFF4-BF2E952BDAC5@xxxxxxxxxxxxx>
<MIME-Version: 1.0
<Content-Type: text/plain;
< charset="Utf-8"
<Content-Transfer-Encoding: 7bit
<X-Newsreader: Microsoft CDO for Windows 2000
<Content-Class: urn:content-classes:message
<Importance: normal
<Priority: normal
<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
<Newsgroups: microsoft.public.windows.server.sbs
<Path: TK2MSFTNGHUB02.phx.gbl
<Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:51664
<NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
<X-Tomcat-NG: microsoft.public.windows.server.sbs
<
<Hi Robert,
<
<I followed your instructions and have now uncovered a number of errors.
<Checking the records in DNS I found that there were some IP addresses
listed
<that no longer exist. (I hope it was okay to delete those.)
<
<I found that the two original PC's that prompted this whole thing for some
<reason show the correct IP address when I run ipconfig on the machine
itself,
<but when I ping the PC's by name, they show up as the other PC. To
clarify,
<when I ping 'MARY' I get the IP address for 'SALLY' and when I ping
'SALLY' I
<get the IP address for 'MARY'.
<
<This is all new territory for me and I hope I didn't mess anything up by
<what I'm trying to do to fix the problem. Here's what I've done so far.
PC1
<wouldn't let me do an ipconfig/ release. It said something to the effect
<that "the requested operation requires elevation". I am the Sys Admin and
<supposedly have full power, so I don't know what that's all about. I
deleted
<the entry on the DNS list for PC2 and changed the IP address on PC1 to
make
<it match what was on the list. I restarted the two DNS services that
appear
<in the list of services (services.msc) and appear to have remedied the
<problem with PC1 and PC2.
<
<I found duplicated IP's in the DNS records, so I deleted the lines for
those
<machines that reported the incorrect IP addresses and for those that
allowed
<me to do it, I ran the IP release, renew, and registerdns commands. I
also
<deleted them from the domain and re-joined them.
<
<I've taken care of all of the duplicate IP's and now every machine name
<reports to the correct IP address. The only problem now is that I have 3
or
<4 other machines that I can't link to remotely.
<
<You've been a tremendous help thus far. The information that you provided
<has helped me to correct most of my current problems and will certainly be
<useful when future problems arise. I would appreciate it though if you
could
<share some insight on why these things might have happened in the first
place.
<--
<Gramps98
<
<
<"Robert Li [MSFT]" wrote:
<
<> Hi,
<>
<> Thanks for your reply.
<>
<> It seems the clients' IP is not correctly registered in DNS.
<>
<> Please let me know the following information:
<>
<> 1. How do you assign DHCP to client workstations, via DHCP on SBS or
<> hardware router?
<>
<> Please check the following:
<>
<> Step 1: Please double confirm the TCP/IP settings on the problematic
<> workstation:
<>
<> 1. Logon the problematic workstation and double-click Internet Protocol
<> (TCP/IP) from the list and click Advanced.
<>
<> 2. Under DNS tab, please ensure clean all the contents in the "Append
these
<> DNS suffixes (in order)" region. Please make sure that "Append parent
<> suffixes of the primary DNS suffix "has been selected. And the option
<> "Register this connection's address in DNS" is checked.
<>
<> 3 After verifying the setting on workstation, please run command
"ipconfig
<> /release" and "ipconfig /renew" to update IP information.
<>
<> 6. Please run command "ipconfig /registerdns" then please check if the
<> issue fixed.
<>
<> Step 2: Please check the records in DNS.
<>
<> 1. Open DNS console.
<> 2. Migrate to Server/Domain.local.
<> 3. On the right side, can you see the A record of the problematic
client?
<> Is the computer name correctly point to the IP?
<>
<> Hope the information helps.
<>
<> If you need further assistance, please don't hesitate to let me know.
<>
<> Best regards,
<>
<> Robert Li(MSFT)
<>
<> Microsoft CSS Online Newsgroup Support
<>
<> Get Secure! - www.microsoft.com/security
<>
<> =====================================================
<>
<> This newsgroup only focuses on SBS technical issues. If you have issues
<> regarding other Microsoft products, you'd better post in the
corresponding
<> newsgroups so that they can be resolved in an efficient and timely
manner.
<> You can locate the newsgroup here:
<> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
<>
<> When opening a new thread via the web interface, we recommend you check
the
<> "Notify me of replies" box to receive e-mail notifications when there
are
<> any updates in your thread. When responding to posts via your
newsreader,
<> please "Reply to Group" so that others may learn and benefit from your
<> issue.
<>
<> Microsoft engineers can only focus on one issue per thread. Although we
<> provide other information for your reference, we recommend you post
<> different incidents in different threads to keep the thread clean. In
doing
<> so, it will ensure your issues are resolved in a timely manner.
<>
<> For urgent issues, you may want to contact Microsoft CSS directly.
Please
<> check http://support.microsoft.com for regional support phone numbers.
<>
<> Any input or comments in this thread are highly appreciated.
<>
<> =====================================================
<>
<> This posting is provided "AS IS" with no warranties, and confers no
rights.
<>
<> --------------------
<> <Thread-Topic: Remote Access Issue
<> <thread-index: AcfKJNlDLOm2hXDnQ4+wpqPFZDrQ1Q==
<> <X-WBNR-Posting-Host: 207.46.193.207
<> <From: =?Utf-8?B?R3JhbXBzOTg=?= <Gramps98@xxxxxxxxxxxxxxxxxxxxxxxxx>
<> <References: <31C459AF-EBC5-4C42-93A3-F3B920FAC585@xxxxxxxxxxxxx>
<> <ORH4#4eyHHA.6140@xxxxxxxxxxxxxxxxxxxxxx>
<> <Subject: RE: Remote Access Issue
<> <Date: Thu, 19 Jul 2007 09:50:01 -0700
<> <Lines: 151
<> <Message-ID: <97D9D9FC-70B2-472A-A17A-1EC78DDFE151@xxxxxxxxxxxxx>
<> <MIME-Version: 1.0
<> <Content-Type: text/plain;
<> < charset="Utf-8"
<> <Content-Transfer-Encoding: 7bit
<> <X-Newsreader: Microsoft CDO for Windows 2000
<> <Content-Class: urn:content-classes:message
<> <Importance: normal
<> <Priority: normal
<> <X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
<> <Newsgroups: microsoft.public.windows.server.sbs
<> <Path: TK2MSFTNGHUB02.phx.gbl
<> <Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:51375
<> <NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
<> <X-Tomcat-NG: microsoft.public.windows.server.sbs
<> <
<> <Robert,
<> <
<> <After reading your response, I noticed that I didn't actually do
<> <"everything" that you asked me too. Having said that, I've now gone
back
<> and
<> <followed your instructions. Here are the results:
<> <
<> <I checked PC1 and wrote down the IP address. From another PC (PC2) I
WAS
<> <able to connect to PC1 with the Mstsc /v (IP_PC1) command.
<> <
<> <I WAS NOT able to connect to that PC when I ran the Mstsc /v
<> (ComputerName).
<> < That particular PC has somehow associated its name with another PC on
our
<> <network.
<> <
<> <I ping'd IP_PC1 and it returned favorable results for the correct IP
<> address.
<> <
<> <One step further, I ping'd the ComputerName for PC1 and it returned the
IP
<> <address for the other PC that it has associated itself with.
<> <
<> <I tried the same scenario on another (3rd) PC on our network. I wrote
<> down
<> <its IP address. I COULD NOT connect to this IP address with the mstsc
/v
<> <IP_PC3 command. I COULD NOT connect using the computer name either. I
<> WAS
<> <able to ping the IP address that I originally wrote down for PC3. When
I
<> <ping'd this 3rd PC by ComputerName, however, it failed and returned a
<> <DIFFERENT IP address than what I originally wrote down.
<> <
<> <Hope that wasn't too confusing. Let me know if I need to elaborate
more.
<> <--
<> <Gramps98
<> <
<> <
<> <"Robert Li [MSFT]" wrote:
<> <
<> <> Hello,
<> <>
- Follow-Ups:
- RE: Remote Access Issue
- From: Robert Li [MSFT]
- RE: Remote Access Issue
- References:
- RE: Remote Access Issue
- From: Robert Li [MSFT]
- RE: Remote Access Issue
- From: Gramps98
- RE: Remote Access Issue
- From: Robert Li [MSFT]
- RE: Remote Access Issue
- From: Gramps98
- RE: Remote Access Issue
- From: Robert Li [MSFT]
- RE: Remote Access Issue
- Prev by Date: VPN - logon as Service
- Next by Date: sbs windows firewall GPO - I want to turn it off.
- Previous by thread: RE: Remote Access Issue
- Next by thread: RE: Remote Access Issue
- Index(es):
Relevant Pages
|
Loading
