?
Solved

Unable to access server from a different subnet

Posted on 2011-09-09
11
Medium Priority
?
757 Views
Last Modified: 2012-05-12
I have 2 wireless routers setup on our network for customer use.  These routers function as DHCP servers so everyones laptop and iPhone aren't using up my IP addresses.  We also have several company computers that the customers can use that are connected via these wireless routers.

We recently switched our DC/DNS/DHCP from a server 2000 machine to a server 2008R2 machine, and since the switch, the SEP clients on these machines are unable to connect to the SEPM management server.  I can ping the server from the command prompt, but thats it.

Our network DHCP runs 192.168.100.X IP addresses, but the wireless routers run 192.168.9.X.

I had other problems with the firewall blocking ports for programs that were on the domain, but was able to resolve those by creating rules.  

Is there something I need to do with the firewall to let it recognize these other subnets?
0
Comment
Question by:schmity78
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
  • 2
11 Comments
 

Author Comment

by:schmity78
ID: 36513428
All the workstations on the domain are able to connect to the SEPM and function fine.
0
 
LVL 14

Expert Comment

by:setasoujiro
ID: 36513591
so if i understand correctly, you are able to ping the other subnet/server 2008 from the clients in the other range?

how are these routers connected to eachother?
is there another firewall/router which connects their "wan'' interface to the same subnet?
0
 
LVL 11

Expert Comment

by:jimbecher
ID: 36513663
  One of the simplest things to try as far as debugging is to stop the firewall service. Don't turn it off. Stop the service. I have seen several cases where people have said it isn't the firwall it is turned off yet it was still functioning. Stopping the service is the sure way to kill it. That will at least tell you if it is a firewall issue.
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 

Author Comment

by:schmity78
ID: 36532719
I am able to ping the server that is in the other subnet.  All of the devices are on the same physical network/LAN.  There is no physical firewall, just the Symantec firewall (and windows firewall, which symantec has taken control of).

I have not had a chance to stop the firewall service, I will try that when there aren't so many people here.

Thanks for the advice so far.
0
 
LVL 14

Expert Comment

by:setasoujiro
ID: 36534102
is it possible that the wireless clients connect using DNS and that you did not setup your local DNS in the wireless router?
0
 
LVL 14

Expert Comment

by:setasoujiro
ID: 36534103
to the sepm i mean
0
 

Author Comment

by:schmity78
ID: 36538568
I checked that yesterday and the wireless router DNS is pointed to our internal DNS servers
0
 
LVL 14

Expert Comment

by:setasoujiro
ID: 36538740
so you can ping the SEPM hostname from the wireless clients that have the issue?
0
 
LVL 11

Accepted Solution

by:
jimbecher earned 1000 total points
ID: 36538756
I am fishing a little but don't you need a static route on your main internet gateway to get stuff back to the respective wireless routers? Was there a route on the 2000 server that no longer exists?
0
 
LVL 14

Assisted Solution

by:setasoujiro
setasoujiro earned 1000 total points
ID: 36538818
@jimbecher, normally of the wifi router handles nat you do not need anymore routes added to the server subnet.

but if the EPSM is trying to reach the clients at 192.168.9.x from the 192.168.100.x subnet, then this is very correct

0
 

Author Comment

by:schmity78
ID: 36539348
Our NAT is handled by our main firewall.   The SEPM is on the .100.X subnet and the clients are on the .7.X subnet.  I can ping the server IP address from the client work station, but the client will not connect.  It wants to connect to port 8014, so I opened that port on the server firewall, but it didnt help.  Maybe there is another port I am not seeing.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
A procedure for exporting installed hotfix details of remote computers using powershell
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
Suggested Courses

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question