Re: DNS Points to itself on SBS
- From: "AC" <gcsokai@xxxxxxxxx>
- Date: Sat, 24 Nov 2007 20:37:15 -0500
Problem solved. I mentioned that we could ping local workstations but not the SBS box, etc below. I was able re-join the server to the domain using connectcomputer wizard by changig its static IP address to one that has not been yet used by DHCP. Previously, I made the mistake of not reserving the old 16.20 static IP address in DHCP. Not sure it this is what the problem was, but it works now. I deleted and re-created the server computer on SBS, joined using connectcomputer, rebooted and we can use both RDP and RWW to reach it.
Thank you all who helped.
Attila
"AC" <gcsokai@xxxxxxxxx> wrote in message news:%23wmEkDwLIHA.4272@xxxxxxxxxxxxxxxxxxxxxxx
So the owner, pretty computer savy, went to the TS, unjoined it from the domain, but when trying to rejoin it using connectcomputer, it cannot find the sbs. It cannot ping sbs by name or by its IP, but it can ping all local workstations by name or IP. It has a static IP assinged, 192.168.16.20, Default GW pointing to the SBS's internal IP.
WHen trying to join it the traditional way, we get an error that the domain controller cannot be contacted. A timeout has expired.
Now Im a bit more confused, whether this be a local DNS problem or what.
Attila
"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message news:u7%23C27vLIHA.5980@xxxxxxxxxxxxxxxxxxxxxxxUse ConnectComputer to join the TS to the domain. Then re-run CEICW, enable the firewall and complete the rest of CEICW. They try RWW again.
--
Merv Porter [SBS-MVP]
============================
"AC" <gcsokai@xxxxxxxxx> wrote in message news:%23FbKamvLIHA.5988@xxxxxxxxxxxxxxxxxxxxxxxNo, it was joined the traditional way, but all the workstations were joined using the wizard. I'll be onsite shortly and provide an update.
"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message news:u1mfd9uLIHA.1204@xxxxxxxxxxxxxxxxxxxxxxxDid you join the TS to the domain using ConnectComputer (which you should do)?
--
Merv Porter [SBS-MVP]
============================
"AC" <gcsokai@xxxxxxxxx> wrote in message news:eYrF9luLIHA.4544@xxxxxxxxxxxxxxxxxxxxxxxI think its just habit, though a good idea to steer TS users towards it. I tried it just now with RWW, and even though I select the name of TS, it logs me on to the domain controller (SBS). I have to do something to resolve this by Monday. Any ideas? Call MS?
Thanks for the help.
Attila
"Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in message news:%23YHC4auLIHA.5716@xxxxxxxxxxxxxxxxxxxxxxxAny reason that you don't use RWW to make the initial connections?
So far, across SBS Land, the hassle factor is:
RWW = very little once the DNS is right, or you could use the public ip of inet facing device.
VPN = a lot
(all hassle definitions are relative, ymmv)
--
Larry
"AC" <gcsokai@xxxxxxxxx> wrote in message news:u0wphLuLIHA.4948@xxxxxxxxxxxxxxxxxxxxxxxI'm working on the issue remotely. I VPN to the network, then use RDP to get to the SBS server and to the TS. I'll check the config based on the suggestions and let you guys know.
"Claus" <cjobes@xxxxxxxxxxxxx> wrote in message news:O$UcsmtLIHA.4880@xxxxxxxxxxxxxxxxxxxxxxxBeside Larry's comments, when you say you try to remote to the TS, where are you trying to do this from? LAN or Outside.
Also, are you running ISA? 1NIC or 2NIC?
--
Claus
"AC" <gcsokai@xxxxxxxxx> wrote in message news:Owk8ursLIHA.3940@xxxxxxxxxxxxxxxxxxxxxxxI recently deployed an SBS 2003 Prem server with a second server acting as TS. When I try to remote to that server, it logs me on to the SBS instead. I am just beginning to troublshoot this issue, but if someone has tips, it would be welcomed. It worked for a week, and just started doing this a day ago.
Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 7062
Date: 11/16/2007
Time: 10:55:07 PM
User: N/A
Computer: TMB
Description:
The DNS server encountered a packet addressed to itself on IP address 192.168.16.2. The packet is for the DNS name "gtnconsulting.com.". The packet will be discarded. This condition usually indicates a configuration error.
Check the following areas for possible self-send configuration errors:
1) Forwarders list. (DNS servers should not forward to themselves).
2) Master lists of secondary zones.
3) Notify lists of primary zones.
4) Delegations of subzones. Must not contain NS record for this DNS server unless subzone is also on this server.
5) Root hints.
Example of self-delegation:
-> This DNS server dns1.example.microsoft.com is the primary for the zone example.microsoft.com.
-> The example.microsoft.com zone contains a delegation of bar.example.microsoft.com to dns1.example.microsoft.com,
(bar.example.microsoft.com NS dns1.example.microsoft.com)
-> BUT the bar.example.microsoft.com zone is NOT on this server.
Note, you should make this delegation check (with nslookup or DNS manager) both on this DNS server and on the server(s) you delegated the subzone to. It is possible that the delegation was done correctly, but that the primary DNS for the subzone, has any incorrect NS record pointing back at this server. If this incorrect NS record is cached at this server, then the self-send could result. If found, the subzone DNS server admin should remove the offending NS record.
Attila
.
- References:
- DNS Points to itself on SBS
- From: AC
- Re: DNS Points to itself on SBS
- From: Claus
- Re: DNS Points to itself on SBS
- From: AC
- Re: DNS Points to itself on SBS
- From: Larry Struckmeyer
- Re: DNS Points to itself on SBS
- From: AC
- Re: DNS Points to itself on SBS
- From: Merv Porter [SBS-MVP]
- Re: DNS Points to itself on SBS
- From: AC
- Re: DNS Points to itself on SBS
- From: Merv Porter [SBS-MVP]
- Re: DNS Points to itself on SBS
- From: AC
- DNS Points to itself on SBS
- Prev by Date: Re: VPN versus Terminal Server for remote workers
- Next by Date: Re: VPN versus Terminal Server for remote workers
- Previous by thread: Re: DNS Points to itself on SBS
- Next by thread: pop3 with custom domain name in exchange?
- Index(es):
Relevant Pages
|
Loading
