This is a revamp of the previous post, i guess I left some information that would make this a little less obvious to resolve.
I have a win2k laptop computer on a subnet trying to reach an ibm mainframe. The computer has connected to the mainframe in the past.There are 30 other people on the same subnet as the laptop connecting to the mainframe. The laptop has the same TCP/IP configuration as the other people in the building that have ip connectivty to the mainframe.
The clients go to a hub with a 1600 router then via point-to-point line to a 2600 router to an unmanaged switch. The mainframe is connected to the switch.There are no access lists or filtering preventing anyone from connecting to the mainframe. The connection is as follows:
laptop---1600----2600---switch---mainframe
The laptop has suddenly lost ip connection to the mainframe. Everything else on the subnet that the mainframe is on, will connect to the laptop. It is only the single ip address that she cannot ping. When I change HER ip host address (in the same subnet), she can connect again to the mainframe. No one else in eight different routed locations has a problem connecting to the mainframe. When I did a traceroute from her machine to the mainframe, the packet gets to the serial interface of the 2600, but dies at the ethernet interface where the switch is connected to the mainframe.
The only thing I can think of is a hardware address issue with her ip address on the switch in the mainframe location. connectivity after changing the ip address tells me it isn't a route table issue.
Any ideas would be appreciated.
I have a win2k laptop computer on a subnet trying to reach an ibm mainframe. The computer has connected to the mainframe in the past.There are 30 other people on the same subnet as the laptop connecting to the mainframe. The laptop has the same TCP/IP configuration as the other people in the building that have ip connectivty to the mainframe.
The clients go to a hub with a 1600 router then via point-to-point line to a 2600 router to an unmanaged switch. The mainframe is connected to the switch.There are no access lists or filtering preventing anyone from connecting to the mainframe. The connection is as follows:
laptop---1600----2600---switch---mainframe
The laptop has suddenly lost ip connection to the mainframe. Everything else on the subnet that the mainframe is on, will connect to the laptop. It is only the single ip address that she cannot ping. When I change HER ip host address (in the same subnet), she can connect again to the mainframe. No one else in eight different routed locations has a problem connecting to the mainframe. When I did a traceroute from her machine to the mainframe, the packet gets to the serial interface of the 2600, but dies at the ethernet interface where the switch is connected to the mainframe.
The only thing I can think of is a hardware address issue with her ip address on the switch in the mainframe location. connectivity after changing the ip address tells me it isn't a route table issue.
Any ideas would be appreciated.