Question

Locked

Networking Nightmare

By Qbert0 ·
I'm a newbe to the game. Started trouble shooting a few networks that were ghost riding along for two years (no admin at all)!
Both were set up by a programing novice who quit right after they were up and running.
The one I need help with went down the week before I started working. It has about 15 workstations (static IPs) running vista connected to one 2003 server performing DC, File/Print Share, VPN, and DNS (or at least thats how it was set up). Will be adding more workstations in the future.
I started by replaceing modem and two 24-port switches. Downloaded all updates (days worth). Tried to Multi-home the NICs the way the other network is set up, but nope. Then updated drivers and tried teaming using Broadcom Advanced Control Suite 2, but it would not give me the option (greyed out). Then tried both on auto config and then just disableing one, but the network is still unreachable. Can't ping any workstations from server, but one teacher workstation can ping server after I changed tcp/ip to auto. Both have internet access. Can't logon to any other workstations. States "there are currently no logon servers available to service the logon request". Can't remote into any either. Teacher's station can remote into server though. All hardware looks to be in working order.
Maybe has to be something to do with the TCP/IP or DNS settings.

Any help would be great.

C:\Documents and Settings\Admin2>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : jhl-server
Primary Dns Suffix . . . . . . . : JeffersonHillsRTC.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : JeffersonHillsRTC.local

Ethernet adapter Internet Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Contr
r
Physical Address. . . . . . . . . : 00-19-B9-3E-44-38
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.72
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 205.171.3.25
205.171.2.25
Lease Obtained. . . . . . . . . . : Tuesday, July 07, 2009 1:40:03 PM
Lease Expires . . . . . . . . . . : Wednesday, July 08, 2009 1:40:03 PM

Ethernet adapter Local Network:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI For Comp
PC Management NIC (3C905C-TX)
Physical Address. . . . . . . . . : 00-0A-5E-3E-96-36
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.65
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Tuesday, July 07, 2009 4:02:23 PM
Lease Expires . . . . . . . . . . : Wednesday, July 08, 2009 4:02:23 PM

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

A couple of questions -

by Deadly Ernest In reply to Networking Nightmare

The first system above is the server, lets call it A and the second is one of the workstations we'll call B.

Everything on B look OK for a system using DHCP to connect through the gateway 192.168.0.1

But I see some major issues with the info on A, and what you do there will depend the answers to the questions below.

1. Is A the DHCP server?
2. Is A the gateway for this network?

Points.

1. If A is the DHCP server it needs to have its own IP address set as static, not DHCP, to 192.168.0.1 so the others can find it and get an address.

If A is not the DHCP server then that's OK.

2. If A is the gateway, then the IP address has to be set as per above.

If A is not the gateway then it has the wrong IP addresses for the DNS servers as they should be the same as for the gateway.

...............

Looking at this, my first guess is system A is the DHCP server and gateway and the only error is its IP address is being obtained via DHCP and should be set as a static IP.

..............

I also suspect the other network was set up using the same system as has the same gateway IP addresses and DHCP capability, and now they are interlinked the servers are fighting over control.

Another point is each NIC has to have it's own IP address.

Hope this helps you.
......................

edit to add

In the past I've connected two small LANs that were separate and now linked. Both had been set up as 192.168.0.x with the dhcp and gateway as 192.168.0.1

What I did was set the IP addresses for the servers as static IP with one being 192.168.0.1 the other being 192.168.0.2 the gateway and dns servers were set as the two addresses, check 192.168.0.1 first then 192.168.0.2 - both were connected to the Internet vis different adsl modems to different ISPs. Later that changed.

Collapse -

I don't see any WINS server

by pnoykalbo In reply to Networking Nightmare

Do you have any WINS server?

Collapse -

don't always need a wins server - I never set one up for a

by Deadly Ernest In reply to I don't see any WINS serv ...
Collapse -

first off, if you are running Active Directory

by CG IT In reply to Networking Nightmare

then the server that runs Active Directory must be listed as the DNS server workstations use to authenticate with and log in to.

Second, teaming NICs is a folly. Undo it. Redundant paths and multiple gateways typically will cause networks to not work. Especially if using non managed switches. Loops which will cause the network to crash can happen with redudant paths. Multiple gateways will cause intermittent Internet outages.

Third is multihome nics on a server are always 2 different subnets. One would be an external interface and one is an internal interface. All workstations use the internal interface. The external interface is where DNS will forward all unresolved queries to the default gateway [which is always the router in front of clients including the server].

So the configuration you show has both network cards the server uses on the same subnet. If your perimeter router is connected to the server using one NIC, and the routers IP address is 192.168.0.1 , then the second NIC IP address should be something different (example 192.168.1.1 or 192.168.10.1 or 192.168.20.1 . This NIC should connect to the uplink port of the network switches [X over cable] and all clients are connected to those switches. DHCP services running on the server should also hand out addresses on this subnet. If you don't know how to create a DHCP scope, authorize and activate it, then I would change the routers addressing scheme. It would be easier to change the routers address and thus the external NIC on the server address then try to deactive and unauthorize a DHCP scope, create a new one, authorize it and activate it.

Collapse -

Uggh, I forgot about AD as I try to keep away from it.

by Deadly Ernest In reply to first off, if you are run ...

I've always found it a BIG problem.

Collapse -

Aw Ernest! well AD is what I do and stay away from

by CG IT In reply to Uggh, I forgot about AD a ...

Netware, eDirectory, OpenDS, Open Directory,
Sun Java Directory Services, and OID as much as I can. ... nothing but problems because nothing is standardized.

Collapse -

IP settings

by BizIntelligence In reply to Networking Nightmare

<b>Points To Be Noted</b>
<br>
On server, for both network cards there are different settings for DNS servers but same for DHCP server.

On first network card (i.e. Broadcom):

DHCP Enabled: Yes
Autoconfiguration Enabled: Yes
Default Gateway: 192.168.0.1
DHCP Server: 192.168.0.1
<b>DNS Servers: 205.171.3.25, 205.171.2.25</b>

On Second network card (i.e. 3COM):
DHCP Enabled: Yes
Autoconfiguration Enabled: Yes
Default Gateway: 192.168.0.1
DHCP Server: 192.168.0.1
<b>DNS Servers: 192.168.0.1</b>

By looking at above information, I think you are using a Router (192.168.0.1) acting as DHCP server as well as DNS server. But you have external DNS settings in first network card i.e. Broadcom

Whereas your Windows 2003 AD server is just acting as file server with unused DNS. Users just logon to it and share files.

<b>SUGGESTIONS</b>

Firstly, you should use your Win2003 as DHCP as well DNS server. It should be properly configured with DHCP scopes and required DNS entries.
You should use separate subnets for each network card. <b>One should connect to Router and other should to LAN</b> (as suggested by CGIT). If you want to use single subnet then connect one LAN card to router and assign default gateway as router. Connect other LAN card to LAN with default gateway as first LAN card IP.

Also, make sure you useStatic IP, gateway,DNS entries for both LAN cards. Even router should have static IP (obvious).

According to you, once WinXP machine can access Win2003 server. So it must have setting matching to one of the network adapter. From there we can find which network settings are correct.
Can you please paste working WinXP Machine ipconfig/all details?

Also, you use VPN. Do you have third party VPN software installed on Windows 2003?
Try to remove it and then check.

Cheers !

Back to Networks Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums