Help!!!! This even has the microsoft boys stumped!!!!

  • Thread starter Thread starter Cameron @ Austral
  • Start date Start date
C

Cameron @ Austral

Hey guys/gals

I have a Windows NT 4.0 server and a Windows 2000 client.
the IP of the client is 192.160.0.1 (Proxy server) and
the Server is 192.169.0.100 (Domain Server).

The Windows 2000 client can see the whole network and
ping any computer on it. The Server can see every other
computer on the network other than the proxy.

No other computer on the network can see the proxy.

What really has me stumped is I can see the proxy in
network neighbourhood on all machines AND BROWSE THE
FILESYSTEM, however still cannot ping it, therefore
tcp/ip networking for this machine is somewhat rooted,
and it is useless as a proxy without this functionality.

Subnet mas is 255.255.255.0 on all machines on the
network including the proxy.

WHAT IS REFUSING THE CONNECTION!!!!????? I have been in a
3m x 3m room with these machines for over 8 hours now and
am going a little loopy, so if you could answer quickly
peoples, I would really appreciate it....... :-)



Thanx

Cameron Holmes
..
 
well, 192.160.0.1 and 192.169.0.100 are not on the same subnet with your
255.255.255.0 mask. have another cup of coffee and recheck all your ip
addresses. also, the normal lan net is 192.168.*.*, i'm not sure who
192.160.*.* or 192.169.*.* are but they may be but our network gateway here
tries to route them outside so i suspect they are public addresses somewhere
so your router is probably trying to send them somewhere else.
 
Hey guys/gals

I have a Windows NT 4.0 server and a Windows 2000 client.
the IP of the client is 192.160.0.1 (Proxy server) and
the Server is 192.169.0.100 (Domain Server).
Click to expand...

Typo, or really a 192.169 and 192.160 subnet? Without routing, you
won't be able to communicate via TCP/IP, though a brodcast may resolve
most of the rest you're looking at.

Jeff
 
What really has me stumped is I can see the proxy in
network neighbourhood on all machines AND BROWSE THE
FILESYSTEM, however still cannot ping it, therefore
tcp/ip networking for this machine is somewhat rooted,
and it is useless as a proxy without this functionality.
Click to expand...

Network neighbourhood is based on NetBEUI, which is not based on IP.
Therefore all hardware seems to be working fine, the problem is probably in
the IP stack of the proxy. Does it have some kind of firewall or filtering
rules installed?

You could try re-installing TCP/IP on the Win2000 machine:
http://www.petri.co.il/reinstall_tcp_ip_on_windows_2000.htm (first one I
could find, there should be better ones around)
 
Hi,
the proxy server needs to be checked. You will have to check the IP on both
the NIC on the proxy server and the connections too.
This should resolve the issue

Manoj
 
Back
Top