RE: NT4 -> 2003 DNS/Domain Name headache

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Joe Wu [MSFT] (joewu_at_online.microsoft.com)
Date: 03/25/04 

Date: Thu, 25 Mar 2004 06:03:21 GMT

Hello Gary,

Thank you for your reply.

Did you enabled IPF or IPSec on the first NIC?

By the way, I would like to suggest that you do NOT use multi-homed PDC as
it may cause further problems. In this case, it is better to disable NIC1
and use NIC2.

Thanks and have a great day!

Regards,
Joe Wu
Product Support Services
Microsoft Corporation

Get Secure! - www.microsoft.com/security

====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
|Content-Class: urn:content-classes:message
|From: "Gary" <gary@silicon.removethisbit.co.nz>
|Sender: "Gary" <gary@silicon.removethisbit.co.nz>
|References: <d23f01c41092$c3be1320$a001280a@phx.gbl>
<XfZ1xkLEEHA.756@cpmsftngxa06.phx.gbl>
|Subject: RE: NT4 -> 2003 DNS/Domain Name headache
|Date: Wed, 24 Mar 2004 14:02:07 -0800
|Lines: 26
|Message-ID: <e5b901c411eb$a5d3bb80$a001280a@phx.gbl>
|MIME-Version: 1.0
|Content-Type: text/plain;
| charset="iso-8859-1"
|Content-Transfer-Encoding: 7bit
|X-Newsreader: Microsoft CDO for Windows 2000
|X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
|Thread-Index: AcQR66XRVGlC3ACbTEOwImH//Y+0Dg==
|Newsgroups: microsoft.public.windows.server.migration
|Path: cpmsftngxa06.phx.gbl
|Xref: cpmsftngxa06.phx.gbl microsoft.public.windows.server.migration:9112
|NNTP-Posting-Host: tk2msftngxa08.phx.gbl 10.40.1.160
|X-Tomcat-NG: microsoft.public.windows.server.migration
|
|Thanks,
|
|I set up some test machines and went through the upgrade.
|
|Ive hit one strange problem - The PDC I used had dual
|onboard NICs, IPs 10.1.1.1 /8 and 10.1.1.2 /8. Only
|10.1.1.1 was connected to the network.
|
|After completing the upgrade there is no communication at
|all through the 10.1.1.1 NIC. It wont even ping the bdc
|(10.1.1.3) or the client (10.1.1.4), and these cant ping
|back to the pdc.
|
|I changed the IP of this nic to 10.1.1.5, but still no go.
|I then changed it to obtain its address from dhcp (from
|dhcp server on the live network), and it can ping in and
|out ok to 'live machines' (192.168.1.x subnet), so it
|doesnt looking like a driver problem.
|
|Finally, I connected the second nic (10.1.1.2) to the
|network, and everything works. The bdc synchronised, the
|client can log on via the pdc, etc etc. Only oustanding
|problem is why the nic connected during the upgrade wont
|allow any connections!
|
|any ideas?
|

Relevant Pages

  • E450 / Solaris 2.7 network problems
    ... When trying to establish TCP connections to the E450 (e.g. xterm session ... The following is a ping of a PC on the LAN; ... 112 packets transmitted, 112 packets received, 0% packet loss ... No known changes have been made to the network, ...
    (comp.unix.solaris)
  • Re: No Internet connection on a laptop
    ... Ipv4 IP Adress 192.168.1.106 ... You can see your signal quality in that network place I described ... IE, which has vulnerabilities you know, and its connections is in Tools/ ... Use the same run cmd to ping: ...
    (alt.comp.hardware.pc-homebuilt)
  • Re: Network Connections window
    ... I can ping other sites and IPs. ... connections in my Network Connections window. ... You may not have permission to use this network resource". ...
    (microsoft.public.win2000.networking)
  • Re: Connection refused
    ... try ping your host from any other box on the network if ping gives a +ve ... then may be you have had firewall which is blocking your connections. ... "Seth" wrote in message ...
    (alt.os.linux)
  • RE: 2 Domains, PDCs cant ping each other
    ... When you say, ping, time out. ... I think it is purely a network issue. ... But the ADM Tool can't find the source domain or the pdc of the source ... PDC of source- and destination-domain also can't ping each other. ...
    (microsoft.public.windows.server.migration)