DMZ to 10.0.0.0 network and visa versa
09 October 2002, 05:19 PM
#1
Scooby Regular
Thread Starter
Join Date: Apr 2001
Location: Northamptonshire
Posts: 630
Likes: 0
Received 0 Likes
on
0 Posts
I have a PC (W2K) in a DMZ, I can connected to a PC on a 10.0.0.0 net for C: access, but not visa versa, server service is running.
Ideas?, because I'm bloody stumped. Even Checkpoint FW-1 dosen't report anything.
Mark
Ideas?, because I'm bloody stumped. Even Checkpoint FW-1 dosen't report anything.
Mark
10 October 2002, 07:51 AM
#4
Scooby Regular
Assuming there is a rule that says something like
Lan --- DMZ ----NBT Accept
DMZ-----LAN ----NBT Accept
It's not likely to be the Firewall. Do both of the machines have the relevant interface of the firewall as their default Gateways ?
Jeff
Lan --- DMZ ----NBT Accept
DMZ-----LAN ----NBT Accept
It's not likely to be the Firewall. Do both of the machines have the relevant interface of the firewall as their default Gateways ?
Jeff
10 October 2002, 09:02 AM
#5
Scooby Regular
Thread Starter
Join Date: Apr 2001
Location: Northamptonshire
Posts: 630
Likes: 0
Received 0 Likes
on
0 Posts
My PC's default gateway is the 10.0.0.1 NIC of the FW, the DMZ pc's is the 192.168.10.1 NIC of the FW.
I have a rule on the FW saying DMZ>PC>ANY>Accept and PC>DMZ>ANY>Accept.
Mark
I have a rule on the FW saying DMZ>PC>ANY>Accept and PC>DMZ>ANY>Accept.
Mark
10 October 2002, 10:20 AM
#6
Scooby Regular
I would try basic network connectivity (Ping, FTP, HTTP etc depending on what's running). If, as I suspect is true, you have basic IP connectivity then you'll need to look at Domain/Workgroup Permissions.
Jeff
Jeff
10 October 2002, 11:23 AM
#7
Scooby Regular
Domain and User Permissions are the most common problems connecting PC to PC. Try using the NET USE command to manually map a drive letter to the other PC's share (you could try the C$ hidden share if you haven't removed it).
That way you can specify the username and password to ensure that you have the proper permission to access the remote PC. Try connecting using the local admin username/password for the remote PC to rule out any Domain security problems.
Stefan
That way you can specify the username and password to ensure that you have the proper permission to access the remote PC. Try connecting using the local admin username/password for the remote PC to rule out any Domain security problems.
Stefan
Thread
Thread Starter
Forum
Replies
Last Post
IWatkins
ScoobyNet General
1
24 October 2000 10:46 AM