Network Issue - Need Help

By soofimra ·
This is shaik.

I have some queries about my office network.

Below is the information to get output from your side as much as possible.

We are using ADSL line connected via fortigate firewall which is isolated by one is internal network (172.16.50.x - can access Internet) and another one is DMZ network (192.168.50.x - cannot access). If I want to access DMZ network, I?ll access via remote software

I have two separate networks in my server.

One is DMZ (ip address: which is connected to my server via CAT5 LAN cable thru switch and another is Dial up which is connected via telephone modem (ip address: is my client network which is used to fetch the file via SFTP).

By default, my server is connected with DMZ network and default gateway also DMZ network gateway( Whenever I'll dial up to client network and the connection is established, the default gateway change to my client network gateway( Then I cannot ping and connect remotely from my system(internal network ip subnet: and gateway: to my server using remote software.

But I want to view my server during the connection established with my client server.

How to rectify this issue? Is it needed to route the client network in my server?

Hope you can assist on this matter.

Thanks in advance.


This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

First: Don't show your email in the forum

by TobiF In reply to Network Issue - Need Help

Unless you're happy to receive spam from bots harvesting this and other sites.
You can edit your post.

Collapse -

RE: First: Don't show your email in the forum

by soofimra In reply to First: Don't show your em ...

Hi TobiF,

Thank you for suggetion


Collapse -

To clarify

by robo_dev In reply to Network Issue - Need Help

Is this a Windows OS Server??

There are several limitations and features of the Windows server OS that may be creating your problem.

First of all, Windows server OS does not do routing by default. It is designed to work with a single WAN interface, and further, it has a feature called 'Dead Gateway Detection'. The combined effect of these two things is that you cannot have two active WAN can only have one default gateway on the client side, and of course the client cannot have multiple routes, as it is not a router.

There are a couple of ways around this. You can enable routing in Windows server OS to allow some limited multi-WAN uasage, and you can define static routes on the client so that you can send traffic where you need to send it to, as the default gateway may not give you access to another subnet.

That being said, the most reliable, secure, and supportable solution is to use a router for routing and not the Windows server.

Collapse -

RE: To clarify

by soofimra In reply to To clarify

Hi Robo_dev,

Thank you for your prompt response.

Our OS is Windows XP SP3. One of network consultant said that he need to route the server machine. But haven't say how?

When try route the system, still the problem is existing.

Any idea to help on this issue?

Thanks again

Collapse -

What do you mean with DMZ?

by TobiF In reply to Network Issue - Need Help

To me, DMZ is not a whole network, but rather a default port forwarding, where a NAT router will forward all incoming traffic to a particular address in the internal network (unless the NAT routing table shows it should go somewhere else).

For instance, if my ISP supplies me a modem with a router, I'll use DMZ to make sure that ALL incoming traffic goes to my own router.

On the "Double directions" question: there was another thread last day that touched the same issue. "Want to hook two residential networks together"

By default, Windows isolate different connections, so that, in general, only one connection is active at any time.

You can add additional entries to the routing table. Open a command window and enter the command ROUTE for a start. But this may be a bit tricky.

Collapse -

What do you mean with DMZ?

by soofimra In reply to What do you mean with DMZ ...

Can you help me that how to route and rectify above posted issue?

Collapse -

The best solution to your problem would be a dual-WAN router

by robo_dev In reply to What do you mean with DMZ ...

If I understand what you are trying to do, you have two WAN interfaces (ISDN and dial-up) and you need to be able to route between the two interfaces.

Windows XP, with a simple registry change, can operate as a simple router. However, this is not very secure and it lacks even the most basic router features, such as load-balancing or automatic failover.

How to enable routing in XP:

Collapse -

humm a consumer DMZ no firewall protection /poster must post more info

by CG IT In reply to What do you mean with DMZ ...

Consumer level routers DMZ actually exposes the host to the internet, without firewall protection so you don't need port forwarding, at least that's how they were back some years ago, I stopped following consumer stuff a year or so ago, just to much trouble with consumer wanting free help.

Corporate is different. Corporate DMZ, depending upon who you talk to is an area behind the perimeter firewall but in front of the local network firewall.

So, DMZ can mean 2 different things.
The poster has got to give more info.

Related Discussions

Related Forums