[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:	DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:	Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:	NETCAD::COLELLADT

Created:	Wed Nov 13 1991
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4455
Total number of notes:	16761

1950.0. "ping,slip,windows problems" by CSC32::D_PERRIN () Tue Jan 31 1995 14:01

    symptom:
    
    hubwatch 3.1 won't work over slip connection between pc and decserver.
    
    486pc. dos 6.2. windows 3.1. slip connection to decserver port from
    com1 port on pc. 
    
    Here's where it gets weird: If Windows
    is not started, ping works in both directions. After Windows is
    started, ping from pc to decserver works intermittently - sometimes 
    the first packet succeeds, sometimes the 20th.
    
    If you reduce the packet size with ping /s, it works better.
    
    Windows is running in 386enhanced mode. If started in standard mode,
    ping works the same as from dos.
    
    Evidently windows is introducing some kind of problem. 
    
    I tried setting tcpwinsize=1 in pwtcp.ini, but it didn't help.
    
    Any suggestions on how to get this to work?

T.R	Title	User	Personal Name	Date	Lines
1950.1	remember it's a PC engine..	PADNOM::PEYRACHE	Jean-Yves Peyrache Country Support Group France	`Wed Feb 01 1995 06:58`	5
	what is the speed of Comm1 ?? jean-yves
1950.2	thanks for the reply	CSC32::D_PERRIN		`Wed Feb 01 1995 10:51`	4
	com1 is set to a lowly 9600 baud. obviously the port on the server is the same. incidentally, a customer reports this using a DECserver 700-8 and I'm using a ds900tm. he's using a 486 and I'm using a 386 but the symptom remains the same.
1950.3	version of DS	PADNOM::PEYRACHE	Jean-Yves Peyrache Country Support Group France	`Thu Feb 02 1995 13:17`	6
	ok it's work (slowly ) for me, have you checked the version of decserver may you havn't the last jean-yves
1950.4	????	CSC32::D_PERRIN		`Thu Feb 02 1995 18:34`	4
	I've got NAS 1.4. It seems to me that the problem lies more with Windows or the ip stack. I don't know much about tuning either. I'm wondering if there's anything in pwtcp.ini that I can adjust.
1950.5	check SWOPS::USER3:[DOCS.V50_DOS_WIN_CLIENT]TCPIP.IP.ps	NETCAD::WAGNERCOFFIL		`Tue Feb 07 1995 10:30`	5
	Take a look at the PATHWORKS V5.0 for DOS and Windows TCP/IP User's Guide. It goes through the PWTCP.INI file in detail. SWOPS::USER3:[DOCS.V50_DOS_WIN_CLIENT]TCPIP.PS Barb