Re: Error 678 The remote computer did not respond
- From: "Mike via WinServerKB.com" <u16958@uwe>
- Date: Wed, 04 Jan 2006 02:44:41 GMT
Also I can telnet to port 1723 when using the IP address but not the DNS name
on port 1723
Mike wrote:
>C:\Documents and Settings\Mike Blanco>nslookup
>Default Server: bgserver1
>Address: 192.168.1.2
>
>> bgchemical.com
>Server: bgserver1
>Address: 192.168.1.2
>
>Name: bgchemical.com
>Address: 192.168.1.2
>
>> www.bgchemical.com
>Server: bgserver1
>Address: 192.168.1.2
>
>Name: www.bgchemical.com
>Address: 192.168.1.2
>
>>What happens when you do an NSLOOKUP on the DNS name that is "linked" to
>>your public IP?
>[quoted text clipped - 4 lines]
>>> figure
>>> out why I can not get authenticated with my dns name.
>
--
Thanks so Much
Mike
Message posted via WinServerKB.com
http://www.winserverkb.com/Uwe/Forums.aspx/windows-server-networking/200601/1
.
- References:
- Error 678 The remote computer did not respond
- From: Mike via WinServerKB.com
- Re: Error 678 The remote computer did not respond
- From: Barry Oxenberg
- Re: Error 678 The remote computer did not respond
- From: Mike via WinServerKB.com
- Error 678 The remote computer did not respond
- Prev by Date: Re: Windows clients randomly go offline?
- Next by Date: Re: Radius Server
- Previous by thread: Re: Error 678 The remote computer did not respond
- Next by thread: Re: Error 678 The remote computer did not respond
- Index(es):
Relevant Pages
|