Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
For some unknown reason my server lost its ip address. I shutdown the server and the firewall - network box and the wired internet box and then powered all back up. The server now has its ip address but now we can not get the network to see the computers on the domain.
sounds like the server is set as a dhcp client.
servers should have statically assigned ip addresses.
these same ip addresses need to be excluded from the dhcp scope so your workstations ips don't conflict with those assigned to the server(s).
How are you configured for tcp/ip?
Is your router providing dhcp to the server and workstations?
what ip address did it have and what ip does it have now?
is this server also running dns server?
are you running Active Directory?
0 
I am not to sure on how to tell about the tcp/ip for you
for ? 2 I do believe we are running dhcp on thre firewall side.
the ip address is the same now as it was before
how can I tell is the dns server is running now?
yes we are runnig active directory.We had a network admin doing all of this for us and he up and quick on me. I am doing what I can as I am some what computer literate. So hope you can work me through the parts I dont know about.
0
Have you changed ANYTHING recently since the admin left?
At a cmd prompt at the server type ipconfig /all and post the results for review.
0
No we have not changed anything. The server lost the ip address sometime over the weekend.
C:\Documents and Settings\amyt>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : *ergman*
Primary Dns Suffix . . . . . . . : companynameLockandKey.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : companynameLockandKey.localEthernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 CT Network Connection
Physical Address. . . . . . . . . : 00-C0-9F-3B-58-F5
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.11*.*
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.111.1
DNS Servers . . . . . . . . . . . : 205.171.3.65
205.171.2.65
Primary WINS Server . . . . . . . : 192.168.0.5
0
according to the ipconfig your server has a static ip assignment so it is not gettings its ip from the router or any dhcp server.
It can't lose its ip address.
It could seem like it lost its ip address if another workstation came up with the same ip of 192.168.111.2
It would appear 192.168.111.1 is your router. Correct?
It would also appear you have another server at 192.168.0.5?
The wins server entry is wrong as well as the two DNS server entries. The wins server is not in your subnet so this is an invalid entry assuming you don't have an additional router and lan in the subnet of 192.168.0.x.
Please post an ipconfig /all from a workstation for comparison. Thanks
BTW ip addresses in the 192.168.x.x range are private ip. Millions of us have the same numbers. You don't want to publish your routers wan ip. That would be a public ip.
0
Yes you are correct on the server # and I dont know what the 192.168.0.5 ip address is.
Windows IP Configuration
Host Name . . . . . . . . . . . . : amylaptop
Primary Dns Suffix . . . . . . . : **rgma**lockandkey.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : **rgma**lockandkey.localEthernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Cont
roller
Physical Address. . . . . . . . . : 00-14-22-ED-DA-65
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.111.12
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.111.1
DHCP Server . . . . . . . . . . . : 192.168.111.1
DNS Servers . . . . . . . . . . . : 205.171.3.65
205.171.2.65
Lease Obtained. . . . . . . . . . : Wednesday, July 08, 2009 11:04:41 PMLease Expires . . . . . . . . . . : Thursday, July 09, 2009 11:04:41 PM
0
Thanks for the post. Your workstations have the same issue the server does which explains why they aren't seeing each other.
They all point to the ISP dns servers for name resolution.
When a computer wants to know where something is it makes a request. The request is recieved by a dns server that looks at its database of entries to then send back the requested information.
Problem with your config is everyone is talking to the isp and not to the local dns server. The isp dns servers know about google.com but don't know about your local server name.
Corrections need to be made on both the server, workstations and the router.
In the router you want to change the dhcp scope which provides the ip and dns information. The dns information should be changed from 205.171.3.65 and 205.171.2.65 to that of the MS server 192.168.111.2
You also need to check that the routers dhcp scope starts at 192.168.111.3 and does not include .2 or .1 as addresses it can lease out [or you will have a ip conflict with the server which will render it inaccessable until a reboot]
You need to change the servers tcp/ip properties.
Remove the invalid wins entry. OK to have it blank unless you are running wins on the MS server then you put the servers ip here.You need to change the servers dns entries to just point to itself at 192.168.111.2
Next you need to go into the MS DNS server [load mmc and the dns module - more on that later if you don't know how] and then the forwarders tab. In here you put the two ISP dns servers of 205.171.3.65 and 205.171.2.65
Once your reboot the router, then the server, then the workstations, name resolution will work correctly. A workstation will ask the ms server for its name and the server will reply. A workstation will ask for google.com and the ms dns server will know it doesn't have that info so it will forward it to the isps dns servers which will reply. The ms server will then pass that info to the workstation.
Let me know what changes you are comfortable making.
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
