Member Avatar for akeem04

Hi all,

I have windows 2003 advance server enterprises edition been installed on dell machine with 2 network card. i connected the internet connection to one of the card and been shared then other to switch. My problem is that i can browse on the server but the workstation can browse. The server is on domain why the cliet computers are on workgroup. CAN SOMEONE HELP ME OUT PLS.

AKEEM

  • 3 Contributors
  • 3 Replies
  • 143 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by DimaYasny

Dani AI

Generated

— common causes when the server can browse but clients cannot are DHCP/gateway/DNS misconfiguration, NAT not enabled on the server-side, or a firewall blocking forwarded traffic. is on the right track about the gateway/subnet and is correct that server-side NAT/RAS is the right tool for a Windows Server 2003 machine — but there are a few targeted checks and fixes to try first.

Do these checks in order on a problem workstation:

  • Run ipconfig /all and confirm the Default Gateway is the server’s internal IP and the DNS server is the internal DNS (domain controller) if you use AD.
  • ping the server internal IP. If that fails, fix LAN connectivity first.
  • ping 8.8.8.8. If this succeeds but nslookup www.google.com fails, it’s a DNS problem; if ping by IP fails, it’s a routing/NAT problem.
  • Temporarily disable firewalls on server and client for testing to rule out packet filtering.

Server configuration notes:

  • Give the internal NIC a static IP and ensure DHCP hands that IP out as the gateway and DNS to clients.
  • Do not rely on ICS on a domain controller. On Windows Server 2003 use Routing and Remote Access (RRAS) and enable NAT on the external interface: Administrative Tools → Routing and Remote Access → configure NAT on the public interface.
  • Verify RRAS shows the external interface as “public” and NAT translation is active. Check event logs for RRAS/NAT errors.

Domain vs workgroup: clients do not need to be domain members to get internet access. If clients are failing to join the domain, that usually points to DNS/gateway issues — fix the above first. If problems persist after these checks, collect ipconfig /all, route print, and a tracert 8.8.8.8 from a client to diagnose further.

Recommended Answers

All 3 Replies

Member Avatar for HoustonIT

Is the server's lan address set as the default gateway on the workstations? is everyone on the same subnet? Have you checked the firewall settings?

Member Avatar for akeem04

Hi Eric,

The system was base on DHCP, the workstation Pc got all the parameter correctly. The Pcs can see each other but yet they can browse.

Member Avatar for DimaYasny

configure RAS with NAT on the server. put the workstations in the domain for access

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.