Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Network Connection Error with XP Proffessional - Urgent Please

Status
Not open for further replies.

xavieb

Programmer
May 24, 2000
4
US
I am having issues with network connectivity and would like advise on this.
My client systems can connect to the internet(DSL) and intranet(IIS web sharing) but network shares are unavailable.
I will outline my whole setup even though am inclined to believe that problem lies within Windows 2000 server DHCP and DNS

setup.

Below is my setup:
__________________
1. DSL connection via DSL router. DHCP is turned off here hence the Efficient router acts as a bridge. A static IP address is

assigned to the router and DNS as provided by ISP.
2. Efficient router connected to Sonicwall firewall. Static IP address and DNS assigned here as perovided by ISP.
DHCP is off on the firewall and NAT configured. LAN IP address 192.168.1.1 is assigned.
3. A connection runs from the firewall to a switch where all client computers and 2000 server are connected.
4. Windows 200 server is assigned a static IP address and DNS as provided by ISP.
I have set up DHCP and DNS on the server.
My DHCP setup includes a range of 192.168.1.115 to 125 with 192.168.1.115 excluded as it is the static UIP address for the

server.
Server Options:
(a) DNS Servers: I entered DNS addresses from ISP.
(b)Router: This is the gateway or LAN IP, 192.168.1.1
(c)WINS/NBNS Servers: this is the static IP address of Windows 2000 server
d) WINS/NBT Node Type: 0x8

Scope Options:
I have configured these the same as server options.
When server options are configured, they are viewable in the scope options. However you cannot edit them. I actually addedd

the same entries here and you can edit this. Is this necessary or a potential problem?


Noted dilemmas and Issues after the above set up:
1. When I ping my servers domain name, should I be able to see a pingable IP address? This is a standalone server. Whenever I

try this, it says the host could not be found.
2. An nbtstat check results in three conflicts all associated with the server. I have performed the steps recommended by

microsoft to fix this but I still have this conflicts.
3. Net view from the server does not display client computers, only the server is displayed.
4. Net view from any client system displays all other client computers but not the server. I can however ping and net send to

the server from client systems and vice versa.
5. Clients cannot connect to network drives but can connect to the internet and intranet.
6. When I attempt to add a computer to the domain, the client computer is unable to find the server.

I hope this gives an expert fairly good idea of what the problem may be. Thanks and I really appreciate the help.



 
All I can think of is to make sure that each computer is a member of either the domain or at least the same workgroup. Also, make sure that the shared folder is giving the correct permissions.
 
Try specifying in your DHCP Scope Options;

Your Server as the DNS server for the workstations

And configure (add) DNS, if you haven't already, create new Forward and Reverse lookup zones with an Internal Domain Name of your choice if you want to stay hidden from the outside world.

Or if you want an External presence (protected by your Firewall) i assume you have a Publically registered Domain Name, use this

In the Properties of your DNS Server in the DNS Snapin you want to add your ISPs DNS servers as 'Forwarders'

On a Win2k Domain you need to have your Win2k Server resolving the internal DNS names of your workstations (in conjunction with WINS for NetBIOS names)

Any Internet queries are automatically forwarded by your Server to your ISPs DNS Servers if it doesn't know the answer to the query.

If you don't have a DNS server configured then you really need documentation on how to do it.

DNS is vital for a Win2k Domain
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top