[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 190
  • Last Modified:

Can't browse domain after new server install.

I have a small network, 3 DC's (2 win 2000, 1 win 2003) and about 90 workstations/servers.  Ever since I installed the new windows 2003 server as the PDC, I am unable to browse the network (through My Network Places, for ex.)  and I can't figure out why.  This definitly began when I set up the 2003 server.  It is not my first 2003 server, as exchange is running on 2003...  I really don't know where to begin to troubleshoot...
0
mchad65
Asked:
mchad65
  • 6
  • 4
1 Solution
 
mcrosslandCommented:
Did you install A/D integrated DNS on the 2003 server?
Is your DNS and Wins pointing to the new server for all servers and workstations?

0
 
mchad65Author Commented:
I did install DNS, (I assume is it AD integrated?) and the server itself is pointing to itself as the primary DNS, however none of the clients are pointing to it for DNS yet.  This includes all the local users.  I think I resolved the browsing issue by enabling the computer browser service on the server.  Now I can browse the domain...
0
 
mcrosslandCommented:
cool.
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
mcrosslandCommented:
Ultimately you will want all the workstations and servers pointing to that as the primary.  You will then be able to turn off the browser service.
0
 
mchad65Author Commented:
I am however still having an issue with it.  The server is accessable fine by everyone in our office, and those accessing via a software vpn client, however a remote office connecting via a L2L VPN can't access the new server.  Can't even ping.  Can't map drives by IP either \\IPADDRESS\sharename.  The other servers are on the same network, same subnet.  I do use a hosts file for resolution of internal resources, as the L2L vpn config uses their ISP's DNS servers...  ANy ideas on this one?
0
 
mcrosslandCommented:
try             tracert IPADDRESS
See where it is hopping.  I bet it dies out at the main gateway.  This means that your gateway doesn't know about the new server's ip address.  Try adding a route to the default gateway of the remote network.  Sounds like you are just using local host files. I don't like doing that personally.  I just add the route to the entire subnet on the firewall or vpn device.
0
 
mchad65Author Commented:
It is a cisco 506e set up to L2L.  I would bet you are right about it failing there.   The problem is this: it is a small office in the UK, they use the VPN to access network shares only.  They do alot of browsing, so it is set up to use their ISP DNS for name resolution.

In the cisco config, the only ACL I have referring to our internal network is this, where 10.1.3.x is the local (UK) network and 10.1.1.x is out (US) network:
access-list vpn_tunnel permit ip 10.1.3.0 255.255.255.0 10.1.1.0 255.255.255.0

What would I need to have in there for a route (if you know cisco)?
0
 
mchad65Author Commented:
tracert doesn't make it past the first hop... (The PIX)
0
 
mcrosslandCommented:
You need to tell the PIX where to go next.  
Try a tracert for a server that you CAN reach and that will be the second hop that the pix will need to know to get to that new server.
Check your route tables on the PIX.
0
 
mcrosslandCommented:
I believe it would be something like this.
IP Route 10.1.1.0 255.255.255.0 nexthopip
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now