Re: TCP/IP connection problem

From: Dirk Munk (munk_at_home.nl)
Date: 09/24/04 

Date: Fri, 24 Sep 2004 10:11:37 +0200

RT Carter wrote:
> I do not know VMS but I am a Network Admin (Microsoft & Novell). We
> moved our workstations to a different building and they are now on a
> different network (was 192.255.1.xxx now 192.255.2.xxx)There are no
> managed hubs between the server (192.255.1.203) and the workstations.

Does this mean you do not have routers between network 192.255.1.0 and network
192.255.2.0 ? If both network addresses are true old style class-C networks,
then they should have mask 255.255.255.0 . And in that case there should be a
router between both networks. In this situation it is likely that the gateway
entry of the VMS system has not been properly setup.

Otherwise you are using supernetting, which is also known as Classless
Interdomain Routing (CIDR), and you will be using a mask like 255.255.254.0. In
fact you will not have two networks, but only one (192.255.1.0) with mask
255.255.254.0. If this is the case, then the mask on the VMS system is not
correct. It all depends on the TCP/IP software on the VMS system if a CIDR mask
can be set. Older versions of UCX could not be setup with CIDR masks.

Furthermore I'm quite sure these IP address ranges have not been officially
registered to your company. You should be using a free range of IP addresses,
like 192.168.x.x, 172.16.x.x. or 10.x.x.x . In the present situation your
workstations will not be able to reach any systems on the internet that have a
address in the range of 192.255.1.0 and 192.155.2.0 (assuming they are connected
to the internet by means of a NAT router & firewall).

If you would change your network addresses, use the class-A 10.x.x.x or class-B
172.16.x.x. addresses. With those ranges you can use subnetting which is usually
allowed on all older TCP/IP stacks (contrary to supernetting).

> The workstations can not ping the VMS server. They can ping all other
> 192.255.1.xxx servers and workstations so the only problem is access
> to the VMS server TCPIP address. Is there some security setting that
> would refuse requests from the different network?

Relevant Pages

  • RE: Event ID 529
    ... The source is clear - workstations that are not part of my ... SBS2003 domain share the same local network (it's a shared local network in ... This kind of issue may be caused by Application logon such as while Outlook ... is connecting to Exchange Server, or this is an automated dictionary attack ...
    (microsoft.public.windows.server.sbs)
  • Re: Adding PC to SBS 2000 domain
    ... There are three workstations that have been working fine for years. ... I have inherited this network and my knowledge is based/limited to SBS ... On the SBS 2000 server I created and new user account and new computer ...
    (microsoft.public.windows.server.sbs)
  • Re: Applying Personal Settings
    ... I wouldn't rule out that or another network ... ruling out the server NIC). ... Running ipconfig /all on the workstations confirms that they're getting DHCP ... with ipconfig results pointing gateway & dns ...
    (microsoft.public.windows.server.sbs)
  • Can connect to smb://192.168.0.112/share but not smb://NYS/share
    ... In Konqueror I get an error if I try to browse the windows network. ... I am not sure if this is an issue with my samba config file(the server ... create mask = 0600 ...
    (comp.os.linux.networking)
  • Can connect to smb://192.168.0.112/share but not smb://NYS/share
    ... In Konqueror I get an error if I try to browse the windows network. ... I am not sure if this is an issue with my samba config file(the server ... create mask = 0600 ...
    (comp.os.linux)