DMZ Problems using NT4

[darren77uk]

Hi,

I'm running on a Windows NT platform, we have 3 machines on our DMZ, on two we can connect fine, but one of them, it seems to be a hit and miss connection.

I am using Windows 2000 to connect to the server, it seems to connect initally, but after a few minutes it seems to close the connection and I see a red cross on the connected share to the server, when I try to double click on the actual share it will not let me access it.

I can ping this machine fine, when I do a network search for other machines on the DMZ I can see them fine, but this particular one I cannot.


Can anyone help me in any way possible, I would be most thankful.

Regards.
Darren

 

[Highland]

Are you accessing the DMZ using a firewall and static routes....?????

If you move the machine onto your LAN does it allow you to connect OK.....?????

 

[darren77uk]

Yes I am accessing the DMZ via a Firewall, I cannot move the machine onto the LAN at this stage as it is a live machine, do you think there can be something wrong with my rulebase?

 

[Highland]

Sounds like it could be a routing/network problem....???? If you run a logon script it might be worth trying to map a drive to the server from this and see if allows the connection and then times-out....???? I would have thought if the rulebase was wrong it simply wouldn't allow the connection in the first place...???? U could also try mapping from one of the other servers and see if this is stable...????? Is it just the 2000 machine that fails...???? (just re-read the problem..!!!) What happens mapping from the server to the 2000 machine...???? Are u already mapping a lot of shares from the 2000 PC..???? I've only recently being using 2000 and have noticed this red-cross appearing on shares, normally they restore when re-selected, I don't know for sure if its a time-out setting or a limit on active shares...?????

 

[darren77uk]

The funny thing is that I can connect to other machines on the DMZ fine and they will not time out on me. Its just this particular machine, I have looked at the routing table and they are similar, so I just don't understand why this is not working.

 

[Jpoandl]

A long shot but worth a try. Maybe there is a physical problem.

Try pinging the problematic server like this:

ping 10.34.0.32 -l 4096 -n 100

When this is finished, check the there is no PACKET LOSS:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss)


Joseph L. Poandl
MCSE 2000

 

[Jpoandl]

Oh..or you can try PATHPING from the Windows 2000 server:

PATHPING servername

This will give you packet loss informat with the HOPS detail information. Joseph L. Poandl
MCSE 2000

 

[darren77uk]

Hi there, I tried pathping and there is 0 packet loss.

 

[Highland]

Is it only the mapping that fails...???? How long before it times-out.....?????

 

[darren77uk]

Yes, I can ping the server name or IP address and it has a 0% packet loss, when I try to browse that particular machine, I cannot see it, but if I browse others in the dmz, I can find them, when I map to this particular machine, it maps but then it times out after 2 mins or so. I am totally lost here.

 

[Jpoandl]

Another long shot here...

Try turning on the browser service. (I had a machine not show up in the browse list one time. I turned on the browse service and it showed up in the browse list. )

Also compare your services on the problematic machine to the services on the working machines. Maybe there is an obvious difference?

You may want to reboot the problematic server if you have not done this in a while.

Hope this helps a bit.. Joseph L. Poandl
MCSE 2000

 

[Highland]

try running the "BROWSTAT" command (from the resource kit), if you run it from each server in ur DMZ it should give you an idea if the "problem" server is functioning properly within the domain.....

If u use BROWSTAT VIEW (and redirect output to a file..!!!) u should be able to see if the servers are participating on the domain properly.....

Hope this helps....................

 

[darren77uk]

I have tried using BROWSTAT, but this shows the machines on the DMZ, and stats that the machine I ran it on is the Master Browser, but still I have no luck in resolving the problem, could it be a DNS issue?!

 

[darren77uk]

By moving onto a class B network and installing a new 2000 DNS server this seems to have resolved the issues that I have been having with connecting to the DMZ.

Thanks all for your help.