Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
NT
apps
dfs
dns
domain
dsmnfpnw
embedded
fsft
mail
misc
oemdsp.preinstall
personalfax
print
protocol.ipx
protocol.misc
protocol.ras
protocol.routing
protocol.tcpip
registry
setup
terminalserv.app.
terminalserv.client
terminalserv.connectivity
terminalserv.domain
terminalserv.misc
terminalserv.prot.rdp
terminalserv.prot.tcpip
terminalserv.setup
terminalserv.user
windowsnt.wntsee
  
 
group : microsoft.public.windowsnt.protocol.tcpip      view archive
page nr. << back    20      21      22      23      24      25      26      27      28   



How to create a Standard TCP/IP Port on Win NT4.0     Thu, 25 Aug 2005 19:57:01 -0700
How can I create a Standard TCP/IP Port on Win NT4.0 for network printier? Currently I am using LPR Port but seems there are some problem for connecting to new printers. Should I use STandard TCP/IP Port and how to create it? Kindly please advise ...

Unable to ping self, can ping others, and others can't ping me     Thu, 25 Aug 2005 12:04:41 -0400
I can ping other people but can't ping myself. I can ping localhost. Others can ping each other but can't ping me. I am running Windows XP Pro. I also can't get out to the internet for web surfing. I can ping my gateway, DNS server, etc. I performed a route print and it looks just like other PCs on the net. ...

Finding netbios name of a remote machine.     22 Aug 2005 03:53:32 -0700
Hello, Say virtual name "vname" associated with virtual ip "vip" is online on a machine named "phyname" with actual ip "phyip" on the same adapter. DNS entries are properly created. From another machine in the same domain, how can I find the actual netbios name of phyname? As far as I tried, nbtstat doesnt ...

How to connect NT server network to internet     Mon, 8 Aug 2005 14:08:03 -0700
Hi, Our main office has a subnet 192.168.101.0 with its own dhcp server and a branch office is connected through frame relay line with cisco routesr to main office. Branch office subnet is 192.168.103.0 with its own DHCP server. This is a NT server 4.0 domain. Now we are in process to get T1 with static I ...

Ping mystery in windows     Tue, 02 Aug 2005 12:13:43 +0200
Could anybody tell me why I get different results (in the windows xp command prompt) when I ping "192.168.1.20" and "192.168.1.020". With the first address I'll get the right answer, but with the second adress I'll get an answer like "ping statistic for 192.168.1.16". Why 16? I'll guess that it must have ...

Destination host unreachable     Sun, 31 Jul 2005 17:01:05 -0700
I'm installing a new Windows Server 2003 and have run into a problem that I can't solve. My network consists of 150 PCs running Windows/98. The previous server was NT running Microsoft Proxy Server V2. We chose to discontinue the NT server completely and setup the W2k3 server from scratch. Everything wa ...

What protocol does the map network drive application for NT use?     Fri, 29 Jul 2005 14:30:14 -0700
Hello, What protocol does the map network drive application for NT use? Thanks, Catherine ...

Ping returns the wrong IP     Thu, 28 Jul 2005 21:13:42 -0400
We are trying to develop a board that controls our product. It is basically a Windows CE device. The hardware turns on and the a built in NIC gets an IP and then the OS loads. We don't have registered MAC addresses yet so we are experimenting with random ones while we wait for our block. The first time ...

The facts you should know about making money online!     Thu, 28 Jul 2005 20:59:03 +0100
-Discover how to get 1 Million visitors without paying a dime in advertising! -Discover how a young 31 years old man just became a millionaire on the Internet... in weeks! He paid cash for a Porsche 911 Carrera convertible and a giant domain with private lake in only 28 days. More than 20,000 people have be ...

CAsyncSocket does not receive UDP packet with source address 255.255.255.255     Thu, 21 Jul 2005 14:51:09 +0200
My problem is that I want the CAsyncSocket in my application to receive the UDP packet #17 that you can see in the sniffer snapshot I attach: As you can see, the problem with that UDP packet is that its source address is 255.255.255.255. So, although the packet arrives to my machine (as shown by the sniffer) ...


page nr.: page nr. << back    20      21      22      23      24      25      26      27      28   
Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us