Re: In-Place Upgrade From Windows 2K Server
- From: Meinolf Weber <meiweb(nospam)@gmx.de>
- Date: Fri, 30 May 2008 17:50:10 +0000 (UTC)
Hello Thomas,
Ok, you have to get rid of the dsl modem ip. These will cause problems like you have. Also you should use the server for DHCP and dsiable it at the router. Use the router only for it's main job, routing. DHCP and DNS is done from the DC without any problem and you are more flexibel in configuration of it. If the router "knows" the way to the internet and the clients the way to the router it will also work.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Hello,
I will try to set the DNS for the clients to be only from the DC. As
for the physical connection, all computers (servers and workstations
alike) are connected to the Linksys router (192.168.1.1). I have 3
workstations and 1 server so I fill up all 3/4 ports (2 workstations
and server) on the router with the last port being an uplink for a
simple switch which has the last workstation and a network printer
connected. The Linksys router is then connected to the DSL modem
(192.168.0.1) to go out to the Internet. The DHCP scope on the Linksys
router is from 192.168.1.201 to 192.168.1.251 with the standard C
subnet mask.
These are the logs after pointing the DNS to the DC only. I am unable
to get rid of the second DNS (192.168.0.1) as this is from the DSL
modem.
As for the ipconfig log from the server:
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI
For
Complete
PC Management NIC (3C905C-TX)
Physical Address. . . . . . . . . : 00-01-02-05-38-63
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::201:2ff:fe05:3863%7
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.101
fec0:0:0:ffff::1%2
fec0:0:0:ffff::2%2
fec0:0:0:ffff::3%2
Finally, this is the client's ipconfig log with the modified DNS
pointer.
Windows IP Configuration
Host Name . . . . . . . . . . . . : INTELWKS02
Primary Dns Suffix . . . . . . . : INTELLIGENCE.NGUYEN.COM
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : INTELLIGENCE.NGUYEN.COM
NGUYEN.COM
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : INTELLIGENCE.NGUYEN.COM
Description . . . . . . . . . . . : Intel(R) PRO/1000 PM Network
Connection
Physical Address. . . . . . . . . : 00-16-76-A2-A4-ED
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::f9bc:6c26:361b:6041%7(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.201(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, May 30, 2008 12:46:13
AM
Lease Expires . . . . . . . . . . : Saturday, May 31, 2008 12:46:11
AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.101
192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Hopefully this gives a better understand of the structure I have.
"Meinolf Weber" wrote:
Hello Thomas,
On the client use only domain internal DNS from the DC NOT the
router. Please post also the unedited ipconfig /all from the server.
All ip's starting with 192.x.x.x, 172.x.x.x or 10.x.x.x are private
and cannot be accessed from the internet, so no problem to post the
complete output.
Please describe more detailed how your network is built up. All
server/workstation on a switch, the switch connected to the router
and the router connected via dsl modem to the WAN?
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Hello again,
My DNS server is running on xxSERV01. The IP is 192.168.1.101.
Doing ipconfig on a client workstation, I would get:
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : x.xx.COM
Description . . . . . . . . . . . : Intel(R) PRO/1000 PM Network
Connection
Physical Address. . . . . . . . . : 00-16-76-A2-A4-ED
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::f9bc:6c26:361b:6041%7(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.201(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, May 30, 2008 12:46:13
AM
Lease Expires . . . . . . . . . . : Saturday, May 31, 2008 12:46:10
AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.101
192.168.1.1
192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Again, 192.168.1.101 is the AD Box running DNS for my network.
192.168.1.1 is the Linksys gateway router and 192.168.0.1 is the ip
for my DSL modem going to WAN.
Do I need a reverse lookup zone as well?
Thanks again in advance.
"Meinolf Weber" wrote:
Hello Thomas,
Active directory is based on DNS, so where is your DNS server, you
MUST have one in the domain? Please post an unedited ipconfig /all
from the server and one client
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties,
and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Hello all,
My workstations seem to have been disconnected from the network
after doing an in-place upgrade of a Windows 2K AD Server to
Windows 2K3 Enterprise. My workstations are giving me: "There are
currently no logon servers available to service the logon
request."
This is my setup.
All computers (servers and workstations) are connected to a
Linksys Gateway Router (in gateway mode) which has a line
connecting to the DSL router.
I already had a working AD when the server (xxSERV01) was Windows
2K.
Now all but one workstations (xxWKS01, xxMOB01) cannot log in
since it can't find an authentication server. xxWKS02 can log in
since I enabled Interactive Logon Cache at 10. I can ping xxSERV01
and even browse shared drives/folders via the Network icon on the
desktop. When I try to remote manage the server from xxWKS02 using
the W2K3 adminpak, it says it cannot connect to the domain.
Please let me know if my setup may be wrong or I have to do
anything different on the W2K3 AD box.
xxSERV01: W2K3 AD with no DHCP (DHCP is from gateway router),
static IP, no DNS, basically a pure account authentication server
xxWKS01: Windows XP Pro SP2
xxWKS02: Windows Vista Ultimate SP1
xxMOB01: Windows Vista Business SP1
All are DHCP and takes IP addresses from the gateway router.
Domain is in the format computername.department.main.com.
Thanks in advance.
.
- Follow-Ups:
- Re: In-Place Upgrade From Windows 2K Server
- From: Thomas
- Re: In-Place Upgrade From Windows 2K Server
- References:
- Re: In-Place Upgrade From Windows 2K Server
- From: Thomas
- Re: In-Place Upgrade From Windows 2K Server
- Prev by Date: Re: In-Place Upgrade From Windows 2K Server
- Next by Date: Re: DFS Replication Topology
- Previous by thread: Re: In-Place Upgrade From Windows 2K Server
- Next by thread: Re: In-Place Upgrade From Windows 2K Server
- Index(es):
Relevant Pages
|